spec_skill
- TypeScript
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill matthew-plusprogramming/monorepo --skill spec- SKILL.md17.7 KB
Overview
This skill authors authoritative implementation specifications (spec.md) from gathered product requirements. It produces TaskSpec, WorkstreamSpec, or coordinates MasterSpec creation depending on scope, and writes the resulting spec into the spec group folder alongside manifest.json and requirements.md. Use it after PM discovery or when refining docs to create testable, implementation-ready contracts.
How this skill works
The skill validates the spec group, reads requirements.md and manifest.json, then extracts problem statements, goals, EARS-style requirements, constraints, and open questions. It generates a spec.md with the appropriate tiered template (TaskSpec, WorkstreamSpec, or MasterSpec orchestration), maps requirements to acceptance criteria and tests, produces a task list, and appends a decision & work log entry while updating manifest.json.
When to use it
- After PM completes discovery and requirements.md exists in a spec group
- When turning product requirements into an actionable implementation contract
- To formalize acceptance criteria, task breakdown, and test plans before engineering work
- When a single workstream requires detailed design and sequence diagrams
- To coordinate multi-workstream efforts and define cross-workstream contracts
Best practices
- Do not duplicate requirements in the spec; reference requirements.md and list IDs
- Choose the spec tier by scope: TaskSpec for 30m–4h tasks, WorkstreamSpec for 4–8h deeper work, MasterSpec for 5+ workstreams
- Make acceptance criteria testable and map each to specific test files
- Include sequence diagrams and interface contracts for complex flows
- Record decisions and timestamps in Decision & Work Log and update manifest.json
Example use cases
- Author a TaskSpec for adding a logout flow: context, ACs, task list, and tests
- Create a WorkstreamSpec for a new API endpoint with sequence diagrams and data models
- Coordinate a MasterSpec that decomposes a large feature into independent workstreams and registers contracts
- Refine an existing spec after stakeholder feedback and append decisions to the log
- Produce a test plan that maps requirements to unit and integration tests for CI validation
FAQ
The spec group must exist with requirements.md and manifest.json present in .claude/specs/groups/<spec-group-id>/.
Where is the spec written?
All outputs are written to .claude/specs/groups/<spec-group-id>/spec.md and manifest.json is updated with spec_complete and a decision_log entry.
How do I choose between TaskSpec, WorkstreamSpec, and MasterSpec?
Pick TaskSpec for small single-file changes, WorkstreamSpec for complex single-workstream features needing diagrams/contracts, and MasterSpec when 5+ workstreams and orchestration are required.
