design-doc-generate

Generate formal design documents from Validate mode work items.

3|1|Updated Jan 23, 2026

Search Tags:#validation #checkpoints #rationale #design-docs #risk-analysis #implementation-plan #domain-modeling

Ready to run

npx skills add https://github.com/4tikhonov/the-minority-report --skill design-doc-generate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-doc-generate
Source: https://github.com/4tikhonov/the-minority-report/tree/main/ontologies/.specsmd/fire/agents/planner/skills/design-doc-generate
Command: npx skills add https://github.com/4tikhonov/the-minority-report --skill design-doc-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of formal design documents for high-complexity work items, reducing hand-written planning time and improving traceability.

Core Features & Use Cases

Structured design outputs: Generates a complete design document with summary, key decisions, technical approach, risks, and an implementation checklist.
Rationale-driven decisions: Requires capturing options, trade-offs, and justifications to guide implementation.
Output artifact management: Saves the resulting design at the designated checkpoint path for review and iteration.

Quick Start

From a Validate-mode work item with high complexity, run the design-doc-generate workflow to produce the design and save it to .specs-fire/intents/{intent-id}/work-items/{id}-design.md.

Frequently Asked Questions about design-doc-generate

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

FAQPage Schema

How do I generate a design doc for high-complexity work items?▼

To generate a design doc for high-complexity work items, run the design-doc-generate workflow from a Validate-mode work item. It automates the creation of formal design documents, reducing hand-written planning time and improving traceability.

What is included in an automated design document?▼

An automated design document includes a structured summary, key decisions, technical approach, risk assessment, and an implementation checklist. It requires capturing options, trade-offs, and justifications to guide implementation.

When do I need to use formal design documents with rationale and risk analysis?▼

You need formal design documents with rationale and risk analysis for high-complexity work items requiring checkpoint design. This ensures decisions across domains are captured with options, trade-offs, and justifications for traceability.

Can I use design-doc-generate to manage domain modeling and implementation plans?▼

Yes, you can use design-doc-generate to manage domain modeling and implementation plans. It implements a structured process with decision capture and domain modeling to produce a comprehensive implementation checklist.

Where are the generated design document artifacts saved?▼

Generated design document artifacts are saved at the designated checkpoint path for review and iteration. The output artifact is automatically saved at .specs-fire/intents/{intent-id}/work-items/{id}-design.md.

What's the best way to capture technical decisions and trade-offs for a project?▼

The best way to capture technical decisions and trade-offs is using a rationale-driven design generation process. It requires capturing options, trade-offs, and justifications within a formal document to guide implementation effectively.