Plan-PRD Pattern: Markdown-Staged Planning Flow

A lightweight, SDLC-aligned planning workflow where each phase of the lifecycle produces a committable markdown staging file that the next command consumes.

Short version: /plan-prd writes a PRD, /plan writes a plan, the tdd-workflow skill implements it, and /pr ships it. Each arrow is a file on disk, not a conversation in memory.

Feature: Markdown Staging Files

Every planning artifact is a plain .md file under .claude/:

.claude/
  prds/      # Product Requirements Documents from /plan-prd
  plans/     # Implementation plans from /plan
  reviews/   # Code review artifacts from /code-review

These files are:

• Plain markdown — readable by humans, diffable in PRs, grep-able at CLI.
• Committable — check them in alongside code so the intent travels with the implementation.
• Composable — each command accepts the previous stage's file as its $ARGUMENTS, so the toolchain composes via paths rather than in-context state.
• Resumable — close the session, open a new one tomorrow, pass the file path back in.

Flow

┌───────────────────────────┐
│ /plan-prd "<idea>"        │  Requirements phase
│  → .claude/prds/X.prd.md  │   Problem · Users · Hypothesis · Scope
└─────────────┬─────────────┘
              │
              ▼
┌───────────────────────────┐