context

name	context
description	Generate context summary for a PRD. Use when user wants to create context, summarize PRD for onboarding, create a cheat sheet, or says 'context PRD-XXX', 'summarize PRD', 'context for PRD'.
argument-hint	[prd id e.g. prd-001]
allowed-tools	Read Grep Glob Bash Write Edit

Generate Context Summary for PRD

Create a concise, scannable context document that gives anyone (new dev, AI agent, reviewer) a quick understanding of a PRD without reading the full document.

Input

• PRD ID: $ARGUMENTS
• If no argument provided, read docs/02_prd/__00_index.md and ask the user which PRD to summarize.

Process

Step 1: Load Sources

1. Read docs/02_prd/__00_index.md to find the PRD file by ID
2. Read the full PRD document
3. Read the implementation plan in docs/03_implement_plan/ if it exists
4. Read existing contexts in docs/04_context/ to avoid duplication

Step 2: Extract Key Information

From the PRD, distill:

• What is being built and why (1-2 sentences)
• Target users
• Core requirements (top 5-7 FRs only, not all)
• Key constraints and dependencies
• Current status and phase

From the implementation plan (if exists):

• Tech stack summary
• Key architectural decisions
• Critical file paths

Step 3: Write Context

Use the template in references/context-template.md.

The context document should be:

• Short — fits on one screen (under 80 lines)
• Scannable — use bullet points, tables, no paragraphs
• Self-contained — reader doesn't need to open the PRD to understand the basics
• Linkable — reference back to PRD and impl plan for full details

Step 4: Save File

• Save to docs/04_context/ctx-<xxx>-<module-name>.md (e.g. ctx-001-ghost-runner-api.md, where 001 matches the prd number)
• If docs/04_context/ doesn't exist → create it