writing-specifications

Technical specifications document requirements, architecture, and implementation details in a structured format. This Skill generates implementation-ready specs using a standardized template with sections covering executive summary, goals, requirements, architecture, security, testing, and deployment—ensuring teams have a complete source of truth for engineering work.

A comprehensive specification includes executive summary, goals, requirements, architecture, security considerations, observability, testing strategy, deployment plan, and governance. This Skill enforces that structure automatically, resolving ambiguities and verifying completeness before submission to prevent incomplete or misaligned documentation.

Specifications require clarifying unclear requirements and design decisions upfront. This Skill asks targeted questions during spec creation to surface and resolve ambiguities, ensuring implementers have unambiguous guidance and reducing rework when engineering begins.

Yes. This Skill integrates with MCP workflows through the Wrangler MCP tool, submitting specifications with type 'specification' and conforming to the SPECIFICATION_TEMPLATE.md structure for consistent, traceable documentation across your engineering process.

Templates enforce consistency across all specifications, making them predictable for readers and reviewers. Standardized sections ensure nothing critical is overlooked and align specs with governance requirements, so every team member knows what to expect and where to find key information.

Specifications capture requirements, constraints, and implementation guidance with executable detail; design documents typically explore options and reasoning. This Skill produces specifications—authoritative, implementable documents that resolve ambiguity and serve as the single source of truth for engineering execution.