design-doc-generate

Generate structured design documents with decisions, risks, and implementation checklists.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/phra/Antigravity-Discord-Bridge --skill design-doc-generate-phra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-doc-generate
Source: https://github.com/phra/Antigravity-Discord-Bridge/tree/main/.specsmd/fire/agents/planner/skills/design-doc-generate
Command: npx skills add https://github.com/phra/Antigravity-Discord-Bridge --skill design-doc-generate-phra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed design documents for complex work items, ensuring all critical aspects are considered before implementation.

Core Features & Use Cases

  • Structured Design Generation: Follows a precise template to create design documents.
  • Decision Rationale Capture: Explicitly documents design choices and their justifications.
  • Risk Assessment: Identifies potential risks and proposes mitigation strategies.
  • Use Case: When a high-complexity work item requires a design review, this Skill will generate a comprehensive design document, including decisions, technical approach, and risks, for approval.

Quick Start

Use the design-doc-generate skill to create a design document for the 'user-authentication' work item.

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 document for a complex software architecture work item?

To generate a design document for a complex software architecture work item, use this Skill to automatically capture key decisions with rationale, define domain models, and outline technical approaches. It structures the document for immediate design review.

What should a technical specification include for high-complexity tasks?

A technical specification for high-complexity tasks should include design decisions with rationale, domain models, technical approaches, risk assessments with mitigations, and implementation checklists. This ensures all critical aspects are reviewed before development begins.

How do I document design decisions and risk assessments before implementation?

You can document design decisions and risk assessments by using this Skill to explicitly record your design choices and justifications. It identifies potential risks and proposes mitigation strategies within a structured template.

Can I automatically create implementation checklists that adhere to existing codebase patterns?

Yes, you can create implementation checklists that adhere to existing codebase patterns. The Skill analyzes your project standards and existing codebase patterns to generate a checklist aligned with your established architecture.

When do I need a structured design document for a software engineering project?

You need a structured design document when a high-complexity work item requires formal design review and approval before implementation. It ensures technical approaches, domain models, and risks are thoroughly evaluated.

Does this design doc generation approach require a specific validation mode to work?

Yes, this design doc generation approach operates in Validate mode to require design review before implementation. It captures key decisions, defines domain models, and identifies risks specifically for complex work items needing approval.