design

Generates an architecture design document from plan/requirements.md and outputs it to plan/design.md.

6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kok1eee/o-m-cc --skill design-kok1eee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/kok1eee/o-m-cc/tree/main/skills/design
Command: npx skills add https://github.com/kok1eee/o-m-cc --skill design-kok1eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a completed requirements.md into a structured architecture design document that guides implementation and reduces ambiguity between requirements and engineering work.

Core Features & Use Cases

  • Designer agent spawn: Automatically spawns a foreground designer subagent configured to follow agents/designer.md and produce plan/design.md.
  • Requirements-driven output: Reads plan/requirements.md, fills gaps where possible, and surfaces unresolved known deficiencies into a dedicated section in the design output.
  • Integration with workflow: Ensures design is produced before implementation, enabling downstream task decomposition and implementation steps.

Quick Start

Create an architecture design from plan/requirements.md and output the result to plan/design.md.

Frequently Asked Questions about design

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

FAQPage Schema
How do I generate a software architecture design document from requirements?▼

To generate a software architecture design document, you need a completed requirements.md file. This skill reads your requirements and uses a designer agent to output a structured design.md, bridging the gap between requirements and engineering.

What is the best way to turn a requirements.md file into a practical architecture?▼

The best way to turn a requirements.md file into a practical architecture is to spawn a foreground designer agent that processes the requirements. It applies architectural reasoning to produce a coherent plan/design.md before implementation begins.

How does the designer agent handle missing information or unresolved issues in the requirements?▼

The designer agent handles unresolved issues by filling addressable gaps where possible and recording remaining known deficiencies. These unresolved issues are surfaced in a dedicated known-deficiencies section of the generated design.md.

Do I need a plan/requirements.md file before using this architecture design process?▼

Yes, you need an existing plan/requirements.md file before starting the architecture design process. The skill is designed to read this specific requirements file to spawn the designer agent and generate the corresponding plan/design.md.

Why should I generate a design document before starting software implementation?▼

Generating a design document before software implementation reduces ambiguity between requirements and engineering work. It ensures a coherent architecture is established, enabling accurate downstream task decomposition and implementation steps.