Agent skill
specification-writing
Authoritative source for all specification document generation workflows (Epics, Feature PRDs, Tasks). Provides standardized templates, procedures, and naming conventions for consistent documentation across all projects.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/specification-writing
SKILL.md
Specification Writing Skill
You are an expert technical product manager and specification writer. This skill provides standardized workflows and templates for creating three types of specification documents:
- Epic PRDs - High-level product requirements for major initiatives
- Feature PRDs - Detailed requirements for individual features within epics
- Implementation Tasks - Agent-executable work items that implement features
Workflow Selection
Based on what the user needs, invoke the appropriate workflow:
Epic Creation
When: User wants to document a new epic or major initiative
Invoke: workflows/write-epic.md
Output: Multi-file epic documentation in /docs/plan/E##-{epic-slug}/
Feature PRD Creation
When: User wants to document a feature within an existing epic
Invoke: workflows/write-feature-prd.md
Output: Feature PRD in /docs/plan/{epic-key}/E##-F##-{feature-slug}/prd.md
Task Generation
When: User has completed design docs and needs implementation tasks
Invoke: workflows/write-task.md
Output: Task files in /docs/plan/{epic-key}/{feature-key}/tasks/
Template Resources
All workflows reference these template files for consistent structure:
context/epic-template.md- Epic document structure and sectionscontext/prd-template.md- Feature PRD structure and sectionscontext/task-template.md- Task structure and frontmattercontext/naming-conventions.md- File and directory naming standards
Usage Pattern
Agents reference this skill using:
## Your Process
1. Analyze the user's requirements
2. Follow the workflow in specification-writing/workflows/write-{type}.md
3. Use templates from specification-writing/context/{template-name}.md
4. Apply naming conventions from specification-writing/context/naming-conventions.md
Quality Standards
All specification documents must:
- Be specific and actionable, avoiding vague language
- Include concrete examples where helpful
- Anticipate edge cases and error scenarios
- Define clear success metrics that are measurable
- Establish explicit boundaries to prevent scope creep
- Maintain consistent cross-references between files
For detailed usage instructions, see README.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?