| name | specification-writer |
| model | opus |
| description | Produces a format-calibrated specification document — Full (5,000-15,000 words, all sections), Lean (1,000-3,000 words, agent-ready), or Minimal (delta + code examples) — matched to the scope and audience of the request. Use when: 'write a spec for this feature', 'spec out this release', 'design the architecture for X', 'document this for the implementation agent'. |
| category | specification-driven-development |
| triggers | ["write a spec for this feature","spec out this release","design the architecture for X","document this for the implementation agent"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"feature_description","type":"string","description":"Description of the feature, release, or system to specify","required":true},{"name":"format","type":"string","description":"Specification format — Full (5000-15000 words), Lean (1000-3000 words), or Minimal (delta + code examples)","required":false}] |
| outputs | [{"name":"specification","type":"ref","format":"cas-ref","description":"Format-calibrated specification document matched to the scope and audience of the request"}] |
Specification Writer Skill
Version: 1.1
Created: 2026-02-02
Updated: 2026-02-16
Author: Manus
Purpose: Write production-ready, A+ quality specifications for software releases
Overview
This skill encodes the pattern for writing comprehensive, technically rigorous specifications that match the quality of Dojo Genesis v0.0.17-v0.0.23. Use this skill when creating specifications for new features, releases, or system components.
Quality Standard: 111/100 (A+)
When to Use This Skill
- Creating specifications for new software versions or releases
- Documenting complex system architectures
- Planning major feature implementations
- Communicating technical vision to development teams
- Ensuring consistency across multiple specifications
Choosing the Right Format
The specification template is a maximum, not a default. Calibrate your format to the scope, audience, and context. Use the appropriate tier:
Full Template: Strategic & Architectural Specs
Use for: Complex systems, new architectures, major releases, multi-component integrations, high-risk decisions
Includes: Vision, goals, success criteria, detailed technical architecture, implementation plan, risk assessment, rollback procedures, monitoring, documentation strategy, appendices
When to choose: Your audience includes stakeholders, architects, or future maintainers who need to understand the "why" and "how." The release is substantial enough to warrant comprehensive documentation. Architecture is novel or the system integration is complex.
Typical length: 5,000-15,000+ words
Lean Format: Implementation-Ready Feature Specs
Use for: Well-understood features, implementation-scoped work, autonomous agent execution, rapid iteration cycles
Includes: Brief context (why this matters), component tables, behavior lists, route/API layouts, code examples, test cases. Skip: preamble, vision section, lengthy risk analysis, extensive documentation strategy
When to choose: The feature is well-scoped and the audience is an implementation agent (human developer or AI). The problem is well-understood. You're optimizing for speed and clarity, not stakeholder alignment.
Typical length: 1,000-3,000 words
Structure (sonnet level chunks):
