spec-writer

Generate structured technical specifications with implementation plans and trade-offs.

7|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Zpankz/mcp-skillset --skill spec-writer-zpankz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/Zpankz/mcp-skillset/tree/main/spec-writer
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill spec-writer-zpankz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual, inconsistent technical documentation often leads to miscommunication, rework, and delayed delivery. The Specification Writer provides a structured approach to creating high-quality documents that clearly convey system design decisions, trade-offs, and implementation plans.

Core Features & Use Cases

  • System Architecture Specs: document component boundaries, data flows, API contracts, and non-functional requirements.
  • Feature Specifications: capture user stories, acceptance criteria, UI/API changes, and testing strategy.
  • Technical Proposals: present solutions with rationale, costs, and alternatives.
  • Design Documents: record design decisions, rationale, and migration considerations.
  • Process Documentation: describe workflows, automation, and governance.
  • Mapping Specifications: map between systems, data models, or platforms. Use cases include ADRs, system design reviews, feature proposals, complex integrations, migrations, and cross-framework mappings.

Quick Start

Provide a complete specification for a new feature by outlining the problem, proposed solution, and an implementation plan.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I write a technical specification for system architecture and API contracts?

This approach structures technical specifications by generating documents with problem statements, solution sections, and implementation plans. It applies to system architecture, feature specifications, and ADRs to eliminate manual, inconsistent technical documentation.

What sections should be included in a feature specification or design document?

Required sections include frontmatter, executive summaries, problem statements, solution sections, implementation plans, trade-offs, success metrics, and references. These components capture user stories, acceptance criteria, and design rationale for complex integrations.

Can I use this to document cross-framework mappings and data models?

Yes, it supports mapping specifications to map between systems, data models, or platforms. This functionality addresses complex integrations, migrations, and cross-framework mappings by providing structured technical proposals with rationale and alternatives.

What is the best way to create an Architecture Decision Record (ADR) with trade-offs?

The best way to create an ADR is to structure technical proposals with rationale, costs, and alternatives. It records design decisions and trade-offs systematically, ensuring system design reviews and feature proposals clearly convey implementation plans.

How do I structure a technical proposal with implementation plans and success metrics?

Structure technical proposals by outlining the problem, proposed solution, and implementation plan. Include trade-offs, success metrics, and diagram annotations to present solutions with rationale, costs, and alternatives for engineering, product, and operations teams.