playbooks

home / skills / mattgierhart / prd-driven-context-engineering / skill_template

SKILL_TEMPLATE skill

/.claude/skills/SKILL_TEMPLATE

This skill helps you generate PRD driven context documents to accelerate AI powered product development and documentation workflows.

npx playbooks add skill mattgierhart/prd-driven-context-engineering --skill skill_template

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.6 KB
---
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].
---

# [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 specs/?

## 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?]

Overview

This skill codifies a PRD-driven context engineering workflow for building AI-powered products. It guides teams through progressive documentation, structured output templates, and quality gates to produce validated context artifacts for downstream development.

How this skill works

The skill walks users through three core steps: define and capture product requirements, populate a reusable output template, and run quality gates and testability checks. It produces a structured output template (field definitions, evidence, and validation steps) and a pass/fail checklist that can be consumed by implementation and handoff workflows.

When to use it

  • Starting a new AI product or feature to ensure requirements translate into usable context
  • Preparing contextual artifacts for model prompting, fine-tuning, or retrieval augmentation
  • Aligning cross-functional teams (product, engineering, design) on concrete deliverables
  • Auditing existing product docs to find gaps before development
  • Handoff from product discovery to implementation and testing

Best practices

  • Keep the core output template concise and machine-readable for downstream automation
  • Capture validation evidence and IDs that map to specs or tests
  • Use the quality gate checklist as acceptance criteria for sprints or PRs
  • Avoid embedding implementation details inside the PRD-level context; keep it product-focused
  • Iterate the template based on feedback from engineers and model evaluations

Example use cases

  • Create a context package for a new conversational agent including intent definitions and test prompts
  • Generate validated feature specs that feed into prompt engineering and retrieval layers
  • Audit an existing feature to produce missing evidence and test cases before deployment
  • Standardize handoff artifacts between product and developer teams for faster implementation

FAQ

What does the output template include?

The template defines each field, the purpose it captures, and how to validate it with evidence or IDs.

How are quality gates enforced?

Quality gates are concrete, measurable checklist items used as acceptance criteria before handoff to engineering or model integration.