Agent skill
spec
Generate an implementation-ready specification from a feature idea
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/spec-coakenfold-p-100226
SKILL.md
Specification Generator
PROSE constraint: Orchestrated Composition — transforms a high-level idea into an implementation-ready blueprint that bridges planning and coding.
Purpose
Create a .spec.md file that serves as a deterministic contract between the
planning phase and the implementation phase. Specs ensure consistent outcomes
regardless of who (or what) implements them.
Process
- Parse
$ARGUMENTSfor the feature name and description - Research the existing codebase for related patterns and conventions
- Identify affected layers (frontend, backend, shared types, tests)
- Generate the spec using the template below
- Write the spec to
docs/specs/<feature-name>.spec.md
Spec Template
# Feature: [Name]
## Problem Statement
[Why this feature is needed — the user or business problem it solves]
## Approach
[High-level strategy for implementing this feature]
## Implementation Requirements
### Core Components
- [ ] [File path] — [What this file does]
- [ ] [File path] — [What this file does]
### API Contracts (if applicable)
- `METHOD /path` — [Description] → [Response shape]
### Data Model Changes (if applicable)
- [Table/collection] — [Fields added/modified]
### UI Components (if applicable)
- [Component] — [Purpose and behavior]
## Acceptance Criteria
- [ ] [Testable criterion]
- [ ] [Testable criterion]
- [ ] [Testable criterion]
## Validation Criteria
- [ ] Unit tests >90% coverage for new code
- [ ] Integration tests for all new endpoints
- [ ] No `any` types introduced
- [ ] All inputs validated at system boundaries
- [ ] Error states handled and tested
## Dependencies
- [External package or service, if any]
## Risks
- [Risk] → [Mitigation]
## Handoff Checklist
- [ ] Spec reviewed and approved
- [ ] Architecture aligns with existing patterns
- [ ] No breaking changes to existing APIs (or migration plan included)
- [ ] Ready for implementation via `/implement-feature docs/specs/<name>.spec.md`
Output
Write the completed spec to docs/specs/ and inform the user they can
implement it by running /implement-feature docs/specs/<feature-name>.spec.md.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
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?