design-document

Convert brainstorming decisions into a structured design document.

4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/uta2000/feature-flow --skill design-document-uta2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-document
Source: https://github.com/uta2000/feature-flow/tree/main/skills/design-document
Command: npx skills add https://github.com/uta2000/feature-flow --skill design-document-uta2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming notes and early decisions often get scattered across chats and documents. This skill centralizes those decisions into a single, maintainable design document that serves as the authority between brainstorming and implementation.

Core Features & Use Cases

  • Converts brainstorming decisions into a structured design document with defined sections.
  • Keeps a single source of truth for design decisions and references to codebase artifacts.
  • Supports a smooth handoff from design to implementation planning and review.

Quick Start

Generate a complete design document from current brainstorming decisions and save it to docs/plans.

Frequently Asked Questions about design-document

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

FAQPage Schema
How do I turn brainstorming notes into a structured design document?

A design document specifies required artifacts for feature development, including an overview, user flow, data models, migrations, patterns, and scope. Capturing these decisions provides a single source of truth and supports a smooth handoff from design to implementation planning and review.

What's the best way to maintain a single source of truth for architecture decisions?

Maintaining a single source of truth for architecture decisions requires centralizing early brainstorming outputs into a structured design document. This approach keeps design decisions and references to codebase artifacts maintainable and authoritative before implementation begins across teams.

Can I use this for planning data models and migrations before implementation?

Yes, you can use this for planning data models and migrations before implementation. The generated design document explicitly includes sections for data models, migration strategies, and patterns, ensuring all architectural decisions are defined prior to coding across teams.

How do I generate a complete design doc and save it to my project plans?

To generate a complete design doc and save it to your project plans, the skill processes current brainstorming decisions and outputs a comprehensive file. It quickly structures the plan and saves the document directly to the docs/plans directory for team access.

When do I need a formal design document for feature development?

You need a formal design document for feature development during the design-phase workflow, specifically before implementation begins. It bridges the gap between brainstorming and coding by capturing architecture decisions, user flows, and scope to align cross-functional teams.