writing-design

Generate a design.md from a template for SuperSpec feature definitions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Serien3/SuperSpec --skill writing-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-design
Source: https://github.com/Serien3/SuperSpec/tree/main/src/superspec/skills/writing-design
Command: npx skills add https://github.com/Serien3/SuperSpec --skill writing-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of structured, architecture-focused design documents to guide software changes, reducing ambiguity and rework.

Core Features & Use Cases

  • Template-driven design docs that enforce consistent structure and sections (Context, Goals, Decisions, Risks, Migration, Open Questions).
  • End-to-end guidance for engineers and designers on how to implement changes with rationale and trade-offs.
  • Output artifact written to the standard path .superspec/<feature>/definition/design.md for integration into the delivery process.

Quick Start

Create a new design document for a feature by following the template and saving it to .superspec/<feature>/definition/design.md.

Frequently Asked Questions about writing-design

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

FAQPage Schema
How do I create a formal software design document to guide implementation?▼

To create a software design document, use a template-driven structure covering context, goals, decisions, risks, migration, and open questions to reduce ambiguity and rework.

What should be included in a design doc for a new software feature?▼

A design doc for a new software feature should include context, goals, decisions, risks, migration strategies, and open questions to provide end-to-end implementation guidance with rationale and trade-offs.

How do I structure architecture documentation for software changes?▼

Structure architecture documentation by applying a standardized template that enforces consistent sections for context, goals, decisions, risks, migration, and open questions to explain how to implement the change.

Where should I save the design.md file in a SuperSpec workflow?▼

You should save the design.md file to the .superspec/<feature>/definition/design.md path, serving as the primary output artifact for integration into the delivery process.

Does this design doc template work for requirements definition and feature specifications?▼

Yes, this design doc template works for requirements definition and feature specifications by applying formal definitions within the SuperSpec workflow to capture architecture decisions and trade-offs.