writing-specs

Generate software specifications and design docs using a 13-step process.

401|41|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/imbue-ai/mng --skill writing-specs-imbue-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-specs
Source: https://github.com/imbue-ai/mng/tree/main/.claude/skills/writing-specs
Command: npx skills add https://github.com/imbue-ai/mng --skill writing-specs-imbue-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

People and teams often struggle to produce clear, consistent, and actionable specifications and design documents. This skill provides structured guidance to write high-quality specs that communicate intent, constraints, and success criteria.

Core Features & Use Cases

  • Structured 13-step process: from problem description to final edits, including conflict handling and outline critique.
  • Create multiple outlines and select the best for clarity and completeness.
  • Guidance on updating existing specs and managing uncertainties and documentation references.

Quick Start

Draft a complete specification for a new feature by following the 13-step process outlined in this skill.

Frequently Asked Questions about writing-specs

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

FAQPage Schema
How do I write a software specification for a complex project?

To write a software specification, you can apply a structured 13-step process that covers problem definition, outline critique, conflict handling, and final edits. This ensures your design docs communicate intent, constraints, and success criteria clearly.

What is the best way to structure a requirements document?

The best way to structure a requirements document is by creating multiple outlines and selecting the most complete one. This approach to writing specifications ensures clarity and thorough coverage of project constraints and success criteria.

How do I update existing specifications and manage uncertainties?

You can update existing specifications by following a guided workflow that manages uncertainties and documentation references. This specification revision process involves critiquing outlines and applying final edits to maintain high-quality design docs.

Do I need YAML frontmatter to generate design docs?

Yes, generating design docs requires YAML frontmatter with name and description fields in SKILL.md. You can also include optional assets like scripts and references to support your specifications throughout the 13-step workflow.

Can I use this for feature specifications of varying complexity?

Yes, you can use this structured 13-step process to craft, critique, revise, and finalize specifications for projects of varying complexity. It handles feature specifications by defining problems, managing conflicts, and producing high-quality design docs.