build-prd
build-prd
Create a Product Requirements Document through collaborative discussion with the user, ending with a complete GitHub issue ready for implementation.
When to Use
- User asks to "create a PRD" or "write requirements"
- Working from a GitHub issue labeled
feature-requestorenhancement - User needs to document requirements before implementation
- Transforming a vague idea into a structured, implementable spec
When NOT to Use
- Issue already has a complete PRD (check for
[PRD]prefix in title) - Pure bug reports — those need reproduction steps, not requirements
- Implementation is already underway — write a spec retroactively instead
Prerequisites
More from fellowship-dev/dogfooded-skills
entropy-check
Sensor — checks doc freshness and computes domain quality grades. Never fixes. Detects staleness, missing coverage, and FlowChad gaps. Updates QUALITY_SCORE.md. Skips inapplicable signals per repo.
17distill
Post-mission audit and distillation — capture mode classifies a completed mission using an 8-code failure taxonomy and writes an audit JSON; analyze mode aggregates audit JSONs into a findings report and creates GitHub issues with recommendations.
15migrate-skill
Move a skill from claude-toolkit plugin (or local .claude/skills) into the dogfooded-skills library, then import it back. Use when consolidating skills into the shared repo.
15skill-builder
Write a high-quality agent skill — covers frontmatter spec, section structure, quality criteria, and common antipatterns.
14popsicle
Agent-native onboarding doc generator — builds coverage maps, health baselines, generated docs, and agent adapters so any AI tool can autonomously navigate your repo.
9setup-harness
Scaffold the knowledge layer for a repo — ARCHITECTURE.md, QUALITY_SCORE.md, enhanced docs/code-structure.md, docs/code-guidelines.md, and FlowChad flow stubs. Gives agents a map, not a 1,000-page manual.
8