writing-specifications

Generate implementation-ready technical specifications using the SPECIFICATION_TEMPLATE.md structure.

4|1|Updated Oct 29, 2025

Search Tags:#design #architecture #specification #requirements #MCP

Ready to run

npx skills add https://github.com/samjhecht/wrangler --skill writing-specifications

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-specifications
Source: https://github.com/samjhecht/wrangler/tree/main/skills/writing-specifications
Command: npx skills add https://github.com/samjhecht/wrangler --skill writing-specifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crafts comprehensive technical specifications that serve as the authoritative source of truth, resolving ambiguities and ensuring implementable guidance for engineers.

Core Features & Use Cases

Structured spec creation with executive summary, requirements, architecture, security, testing, deployment
Resolves ambiguities via questions and clarifications
Uses MCP specification templates to enforce consistency
Verifies completeness and alignment with governance before creation

Quick Start

Use the MCP tool to create a specification with a clear executive summary and requirements

Frequently Asked Questions about writing-specifications

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a technical specification for a feature or system design?▼

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.

What should a technical specification include?▼

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.

How do I resolve ambiguities when writing specifications?▼

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.

Can I use specifications with MCP workflows?▼

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.

Why is a specification template important for engineering teams?▼

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.

What's the difference between a specification and a design document?▼

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.