agentleFS
Sign inStart free
hardness1020hardness1020/VibeFlow/.claude/skills/define-prd/SKILL.md

define-prd

Skill8 starsChanged 8 months agoMITView on GitHub

Create PRDs with success metrics for Stage A of the VibeFlow docs-first workflow

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create PRDs with success metrics for Stage A of the VibeFlow docs-first workflow.

    line 15
  2. Distinctive:

    Document requirements, dependencies, and risks

    line 22
  3. Very specific:

    After completing Stage A, update docs/workflow-state.yaml:

    line 72
  4. Distinctive:

    After completing this stage, ask the user for permission before committing:

    line 79
  5. Very specific:

    After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

define-prd

Create PRDs with success metrics for Stage A of the VibeFlow docs-first workflow.

Purpose

This skill creates and validates PRD (Product Requirements Document) for Stage A:

  • Define problem, users, and scope
  • Set success metrics with baseline → target
  • Document requirements, dependencies, and risks

Workflow

Stage A: Initiate
    │
    ├── Create/update PRD
    ├── Define problem, users, scope
    └── Set success metrics

Usage

Create PRD

/define-prd

Creates or updates docs/prds/prd.md with required sections.

Document Requirements

PRD (docs/prds/prd.md)

Required sections:

  • Header (version, file, owners, last_updated)
  • Summary (3-5 lines)
  • Problem & Context
  • Users & Use Cases
  • Scope (MoSCoW format)
  • Success Metrics (baseline → target)
  • Non-Goals
  • Requirements (functional + non-functional)
  • Dependencies
  • Risks & Mitigations
  • Analytics & Telemetry

Validation

  • scripts/validate_prd.py — Validate PRD structure and content

References

See assets/:

  • prd-template.md — PRD template

Manifest Update

After completing Stage A, update docs/workflow-state.yaml:

  • Set stage: A
  • Set docs.prd: docs/prds/prd.md

Git Commit

After completing this stage, ask the user for permission before committing:

git add docs/prds/prd.md docs/workflow-state.yaml
git commit -m "feat(prd): define product requirements (#ft-<ID>)"

Replace <ID> with the actual work item ID.

Auto-Advance

After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free