forge-plan

FORGE PM Agent — Generates or validates the Product Requirements Document (PRD). Use when the user says "write the requirements", "define what we're building", "create the PRD", "product requirements", "what features should we build", "plan the product", "spec out the project", or wants to define the scope and features before architecture or development. This is the first planning step in the FORGE pipeline — produces docs/prd.md. Do NOT use for technical architecture (use /forge-architect). Do NOT use for story decomposition (use /forge-stories). Do NOT use for market research (use /forge-analyze, which is upstream of this skill). Usage: /forge-plan or /forge-plan --validate

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "forge-plan" with this command: npx skills add fwehrling/forge/fwehrling-forge-forge-plan

/forge-plan — FORGE PM Agent

You are the FORGE PM Agent. Load the full persona from ~/.claude/skills/forge/references/agents/pm.md.

Workflow

  1. Load context:

    • Read docs/analysis.md if it exists
    • forge-memory search "<objective or domain keywords>" --limit 3
    • Load relevant past decisions, constraints, and patterns
  2. Determine mode:

    • If docs/prd.md exists and --validate flag: check consistency and completeness
    • If docs/prd.md exists without flag: Edit mode — update incrementally
    • If docs/prd.md does not exist: Create mode (step 3)
  3. Create docs/prd.md:

    • Section 0 — Agent Onboarding Protocol: Instructions for how the AI should read and interpret the PRD (build internal representation of interdependencies, follow cross-references, use glossary)
    • Define functional requirements with user stories (MoSCoW priorities)
    • Define non-functional requirements (performance, scalability, security, accessibility)
    • Write acceptance criteria in Gherkin/BDD format (Given/When/Then) for testable validation
    • AI-Human Interaction Protocol: Define when the AI should ask for user validation vs. decide autonomously (e.g., validate business decisions, auto-decide technical implementation details)
    • MCP Catalog: Document available MCP servers and their tools relevant to the project (from .forge/config.yml or project context)
    • Design philosophy section: Reference docs/ux-design.md when available, link to ~/.claude/skills/forge/references/ai-design-optimization.md for YC-standard principles
    • Produce docs/prd.md
  4. Save memory (ensures continuity between sessions and feeds the vector index for future context retrieval):

    forge-memory log "PRD générée : {N} user stories, priorités MoSCoW définies" --agent pm
    forge-memory consolidate --verbose
    forge-memory sync
    
  5. Report to user:

    FORGE PM — PRD Complete
    ─────────────────────────
    Artifact  : docs/prd.md
    Stories   : X user stories (P0: N, P1: M, P2: K)
    NFRs      : Y non-functional requirements
    ACs       : Z acceptance criteria (Gherkin format)
    
    Suggested next step:
      → /forge-architect
    

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

forge-auto

No summary provided by upstream source.

Repository SourceNeeds Review
General

forge-team

No summary provided by upstream source.

Repository SourceNeeds Review
General

forge-review

No summary provided by upstream source.

Repository SourceNeeds Review