.claude/skills/SKILL_TEMPLATE/SKILL.md
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
npx skillsauth add mattgierhart/PRD-driven-context-engineering prd-vXX-skill-nameInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
[One sentence summary of the skill's purpose.]
[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.
[Detailed instructions for this step]
[Detailed instructions for this step]
[Detailed instructions for this step]
| Pattern | Example | Fix | |---------|---------|-----| | Bad pattern 1 | "Example" | → "Better approach" | | Bad pattern 2 | "Example" | → "Better approach" |
references/[file].md — [Description of when to use]assets/[template].md — [Description of template purpose][What happens after this skill completes? What stage/skill comes next?]
tools
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.
development
Define success criteria and tracking setup for launch during PRD v0.9 Go-to-Market. Triggers on requests to define launch metrics, set up tracking, or when user asks "how do we measure launch success?", "launch KPIs", "tracking setup", "success criteria", "analytics", "launch goals". Outputs KPI- entries specialized for launch measurement.
development
Define go-to-market strategy including launch plan, messaging, channels, and timing during PRD v0.9 Go-to-Market. Triggers on requests to plan launch, define GTM strategy, or when user asks "how do we launch?", "go-to-market", "launch plan", "marketing strategy", "messaging", "launch channels", "GTM". Outputs GTM- entries with launch plan components.
development
Establish channels and processes for capturing and processing post-launch feedback during PRD v0.9 Go-to-Market. Triggers on requests to set up feedback systems, capture user input, or when user asks "how do we collect feedback?", "feedback loop", "user research", "post-launch feedback", "customer feedback", "NPS", "voice of customer". Outputs CFD- entries specialized for post-launch feedback capture.