ReddRadar
Agent skill
prd-vXX-skill-name
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Install this agent skill to your Project
npx add-skill https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/SKILL_TEMPLATE
SKILL.md
[Skill Name]
[One sentence summary of the skill's purpose.]
Workflow Overview
- Step 1 → Brief description
- Step 2 → Brief description
- Step 3 → Brief description
Core Output Template
[Define the primary output structure this skill produces]
| Element | Definition | Evidence |
|---|---|---|
| Field 1 | What this captures | How to validate |
| Field 2 | What this captures | How to validate |
See assets/output-template.md for copy-paste template.
Step 1: [First Major Step]
[Detailed instructions for this step]
Checklist
- Item 1
- Item 2
Step 2: [Second Major Step]
[Detailed instructions for this step]
Step 3: [Third Major Step]
[Detailed instructions for this step]
Quality Gates
Pass Checklist
- Gate 1: [Specific, measurable criterion]
- Gate 2: [Specific, measurable criterion]
- Gate 3: [Specific, measurable criterion]
Testability Check
- Can this output be validated?
- Does it reference IDs from SoT/?
Anti-Patterns
| Pattern | Example | Fix |
|---|---|---|
| Bad pattern 1 | "Example" | → "Better approach" |
| Bad pattern 2 | "Example" | → "Better approach" |
Bundled Resources
references/[file].md— [Description of when to use]assets/[template].md— [Description of template purpose]
Handoff
[What happens after this skill completes? What stage/skill comes next?]
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
mattgierhart/PRD-driven-context-engineering
prd-v05-technical-stack-selection
Make technology decisions for every product capability by discovering existing assets, evaluating vendor-aligned options, and categorizing as Reuse/Extend/Build/Buy/Integrate/Research during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on "tech stack", "build or buy?", "what technologies?", "technical decisions", "what do we reuse?", "existing stack", "vendor constraint", "IBM-first", "what tools do we need?", "evaluate solutions", "select tech stack". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and cross-references. Feeds v0.6 Architecture Design.
mattgierhart/PRD-driven-context-engineering
ghm-harvest
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.
mattgierhart/PRD-driven-context-engineering
ghm-status-sync
Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.
mattgierhart/PRD-driven-context-engineering
prd-v02-product-type-classification
Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Triggers on PRD v0.2 work after competitive analysis, or when user asks "what type of product should we build?", "should we clone or innovate?", "is this a fast-follow opportunity?", "how should we position against competitors?", "clone vs undercut", "unbundle vs slice", or requests help choosing product strategy. Outputs BR- entries for product type classification and inherited GTM constraints.
mattgierhart/PRD-driven-context-engineering
prd-v03-outcome-definition
Define measurable success metrics (KPIs) tied to product type during PRD v0.3 Commercial Model. Triggers on requests to define success metrics, set KPI targets, determine what to measure, establish go/no-go thresholds, or when user asks "how do we measure success?", "what metrics matter?", "what's our target?", "how do we know if this works?", "define KPIs", "success criteria". Consumes Product Type Classification (BR-) from v0.2. Outputs KPI- entries with thresholds, evidence sources, and downstream gate linkages.
mattgierhart/PRD-driven-context-engineering
prd-v05-risk-discovery-interview
Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5 Red Team Review. Triggers on requests to identify risks, stress-test the idea, perform red team review, or when user asks "what could go wrong?", "identify risks", "red team", "risk assessment", "challenge assumptions", "stress test the idea". Consumes all prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as interview context. Outputs RISK- entries with owner decisions and mitigations. Feeds v0.5 Technical Stack Selection.
Didn't find tool you were looking for?