skills.rest
nesnilnehc
nesnilnehcCOMMUNITY
Explore all skills by this author →
GitHub

design-solution

Generate a design document with architecture, components, data flows, and trade-offs.

7|3|Updated Jan 23, 2026
Search Tags:#design#architecture#documentation#requirements#trade-offs#design-doc
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill design-solution-nesnilnehc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-solution
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/design-solution
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill design-solution-nesnilnehc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produce a validated design document from requirements (architecture, components, data flow, trade-offs) with no implementation. Use when requirements are clear and you need a single source of truth for downstream task breakdown.

Core Features & Use Cases

  • Structured design workflow: converts validated requirements into a cohesive design document detailing architecture, components, data flows, and trade-offs.
  • Trade-off analysis: presents 2-3 alternative approaches with pros, cons, and recommended option.
  • No-implementation boundary and traceability: outputs are ready for downstream breakdown without any code and can reference validated requirements.

Quick Start

Generate a design document from the validated requirements, capturing architecture, components, data flow, and trade-offs without any implementation details.

Frequently Asked Questions about design-solution

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

FAQPage Schema
How do I convert validated requirements into a design document?▼

A design document serves as a single source of truth for architecture decisions and downstream task breakdown. It details components, data flows, and trade-offs while maintaining a strict no-implementation boundary to guide approvals.

What's the best way to document architecture trade-offs during design?▼

To create a design doc, apply a structured workflow to your validated requirements that evaluates 2-3 alternative design approaches with pros and cons, then outputs the recommended architecture to a dated markdown file in your docs directory.

Can I generate a design doc that includes code implementation details?▼

A design doc should be created when your requirements are fully validated and clear. Use it to establish a single source of truth that drives downstream task breakdown and secures design approvals before any implementation begins.

Where should I save generated architecture design documents?▼

No, this design workflow enforces a strict no-implementation boundary. It focuses exclusively on architecture, components, data flows, and trade-offs to ensure the output remains a pure source of truth for downstream task breakdown.

Related Skills

Explore More Design & Creative Skills→
trueratruera
3.5k

trulens-dataset-curation

Create and curate ground-truth evaluation datasets for TruLens.

Official
Intermediate
sirkirbysirkirby
62

task-decomposition

Convert OAK implementation plans into structured tasks.md files.

Community
Basic
jiaxiaojunQAQjiaxiaojunQAQ
75

architecture-diagram-creator

Generate architecture diagrams from natural language prompts.

Community
Intermediate
cy-walicy-wali

architecture

Generate Architecture Decision Records documenting technology decisions with trade-offs.

Community
Advanced