prd-vXX-skill-name
$
npx mdskill add mattgierhart/PRD-driven-context-engineering/prd-vXX-skill-nameAnalyzes and processes files based on specific triggers to generate structured outputs
- Solves tasks by reacting to predefined phrases or contexts in user input
- Leverages Read, Write, Edit, Glob, and Grep tools for file manipulation
- Decides actions based on matching triggers and file content patterns
- Delivers structured output templates with validated fields and evidence
SKILL.md
.github/skills/prd-vXX-skill-nameView on GitHub ↗
--- name: prd-vXX-skill-name description: > [1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces]. context: fork allowed-tools: - Read - Write - Edit - Glob - Grep --- # [Skill Name] [One sentence summary of the skill's purpose.] ## Workflow Overview 1. **Step 1** → Brief description 2. **Step 2** → Brief description 3. **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?]
More from mattgierhart/PRD-driven-context-engineering
- ghm-gate-check>
- ghm-harvest>
- ghm-id-register>
- ghm-sot-builder>
- ghm-status-sync>
- ghm-template-sync>
- prd-v01-problem-framing>
- prd-v01-user-value-articulation>
- prd-v02-competitive-landscape-mapping>
- prd-v02-product-type-classificationClassify 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.