Skip to content
Back to skills

Product Loop

ASecurity

Run product discovery, PRDs, launches, and learning; decide build or stop.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsrustgorailsgitdocumentation

Security analysis

A100/100

Pro scans all 8 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add fmind/dot --skill product-loop --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Product Loop?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Product Loop
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fmind-product-loop/badge)](https://www.skillsdirectory.com/skills/fmind-product-loop)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: product-loop
description: "Run product discovery, PRDs, launches, and learning; decide build or stop."
license: MIT
metadata:
  kind: task
  author: Médéric HURIER (Fmind)
  source: github.com/fmind/dot/tree/main/skills/product-loop
  created: "2026-08-09"
  updated: "2026-10-06"
---

# Product Loop

Move a product bet through discovery, specification, launch, and learning. Enter at the phase supported by the evidence and make the next decision; [implementation-plan](../implementation-plan/SKILL.md) owns repository execution planning.

## Workflow

1. **Recover the bet**: identify the user, painful job, proposed outcome, constraints, current evidence, and the decision being made.
1. **Select one phase** from the table; read its procedure and the relevant [brief](references/briefs.md), omitting sections that add no useful information.
1. **Test the premise**: distinguish observations, supplied evidence, inference, and assumptions; compare a smaller change and a credible no-build path.
1. **Define the decision**: choose a behavioral outcome, segment, time box, success threshold, guardrails, and evidence that would stop or reverse the plan.
1. **Close the phase** with the decision, its evidence, remaining uncertainty, and the smallest next step within the user's scope.

| Situation                                      | Read when needed                                                                         | Decision                                     |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------- | -------------------------------------------- |
| Problem, demand, or wedge is unproven          | [Discover](references/discover.md), [demand tests](references/demand-tests.md)           | Build, test first, park, or stop             |
| Validated intent needs a behavioral spec (PRD) | [Specify](references/specify.md)                                                         | Requirements, acceptance, and open decisions |
| Built capability needs a bounded audience      | [Launch](references/launch.md), [production-readiness](../production-readiness/SKILL.md) | Launch, limit exposure, or hold              |
| An experiment or launch produced results       | [Learn](references/learn.md)                                                             | Continue, iterate, pivot, stop, or extend    |

## Gotchas

- **Ground every claim in evidence**: never invent quotes, metrics, demand, customer research, availability, or support capacity; effort and traffic alone do not prove customer value.
- **Gate external effects on authorization**: drafts and local planning artifacts are reviewable work. Customer contact, CRM changes, publication, advertising, and spend require authorization for those effects.
- **Preserve the predeclared test design**: retain the original hypothesis, baseline, denominators, segment, thresholds, and uncertainty; explain deviations after observing results.
- **Scale briefs to the change**: compact changes need compact briefs; preserve material trust boundaries, edge cases, and unresolved risks.

## Documentation

- [Source methods](references/sources.md)
- Companion skills: [research-brief](../implementation-plan/references/research-brief.md), [product-design-review](../product-design-review/SKILL.md), [github-issues](../github-issues/SKILL.md).

Files in this skill

  • SKILL.md3.2 KB
  • references/briefs.md2.8 KB
  • references/demand-tests.md3.3 KB
  • references/discover.md1.7 KB
  • references/launch.md2.2 KB
  • references/learn.md2 KB
  • references/sources.md1.6 KB
  • references/specify.md2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…