danielfortizv/sdd-comparative-study/spec-writer
Claude Code and agent skill by danielfortizv/sdd-comparative-study
- community
Checking that the SKILL.md file is still in the repository.
Create or update .spec.md files from clarified requirements. Use when requirements have been gathered and confirmed, and specs need to be written or updated before implementation begins. Produces well-structured spec files with frontmatter, requirements, and test links. Common triggers: "write the spec", "update the spec", "create a spec for", or after requirement-gathering completes.
Install
npx vskill@latest install danielfortizv/sdd-comparative-study/spec-writerSKILL.md
Spec Writer
Create and maintain .spec.md files that capture functional requirements and link to their verification tests.
When to use
- After
requirement-gatheringproduces confirmed requirements - When existing specs need updating due to changed requirements
- When implementation revealed gaps that need documenting
Steps
- Determine scope. Decide whether to create a new spec or update an existing one. One spec per logical unit of functionality — don't combine unrelated features.
- Write frontmatter. Every spec requires YAML frontmatter:
```yaml
name: Feature Name description: Brief description of what this spec covers targets:
- ../src/path/to/implementation.py
- ../src/path/to/related/**/*.py
```
name: Human-readable feature namedescription: One-line summarytargets: Relative paths or glob patterns to implementation files. At least one required.
- Document requirements. Write clear, scannable requirements:
- Start with an API contract code block if there's a public interface
- Use headings to organize by feature area
- Be specific about expected behavior and edge cases
- Describe error handling expectations
- Link tests. Add
[@test]links inline, next to the requirements they verify:
```markdown
- Invalid passwords return 401
[@test] ../tests/test_auth_invalid_password.py ```
- Review against styleguide. Check the spec against the Spec Styleguide: concise, scannable, context around test links, clear headings, specific about behavior, granular test files.
- Save the spec. Place spec files in the project's
specs/directory with a.spec.mdextension.
Complete example
def add_item(cart_id: str, product_id: str, quantity: int) -> Cart: ... def remove_item(cart_id: str, product_id: str) -> Cart: ... def checkout(cart_id: str, payment_method: str) -> Order: ...
Spec format reference
See Spec Format for the complete format specification.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingCalculadora/Etapa 2/Tessl/.tessl/plugins/tessl-labs/spec-driven-development/skills/spec-writer/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/danielfortizv/sdd-comparative-study/spec-writer)