2-design

Generate 2-3 architectural design options with trade-offs for milestone planning.

6|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/DuongMQuang/quangflow --skill 2-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 2-design
Source: https://github.com/DuongMQuang/quangflow/tree/main/plugins/quangflow/skills/2-design
Command: npx skills add https://github.com/DuongMQuang/quangflow --skill 2-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and compare architectural options for a milestone, balancing trade-offs and selecting patterns that support future growth and maintainability.

Core Features & Use Cases

  • Evaluate multiple architecture options and document their trade-offs for informed decision-making.
  • Research and justify applicable design patterns, documenting their benefits and costs.
  • Generate 2-3 concrete DESIGN.md drafts (milestone-2) with rationale, scalability considerations, and integration notes.

Quick Start

Draft 2-3 architecture options for the milestone, including chosen patterns and rationale, then prepare a review-ready DESIGN.md.

Frequently Asked Questions about 2-design

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

FAQPage Schema
How do I compare architectural options for a feature milestone?

To compare architectural options for a feature milestone, you evaluate 2-3 design choices by documenting their specific trade-offs, ensuring alignment with previous milestones, scalability gates, and chosen patterns for informed decision-making.

What's the best way to document design trade-offs and pattern research?

The best way to document design trade-offs and pattern research is to generate a review-ready DESIGN.md draft that includes your architectural rationale, scalability considerations, and the benefits and costs of integrated design patterns.

When do I need to generate architecture design drafts for scalability?

You need to generate architecture design drafts for scalability during Phase 2 design planning, specifically when evaluating how multiple architectural options support future growth, maintainability, and pattern integration for a feature milestone.

Can I use this approach to align my milestone with previous design requirements?

Yes, you can use this architectural design approach to explicitly align your current milestone with previous design requirements by evaluating tensions and ensuring chosen patterns meet established scalability gates.

What are the limitations of planning architecture without explicit trade-offs?

Planning architecture without explicit trade-offs limits your ability to justify design patterns, balance future growth against maintainability costs, and generate concrete DESIGN.md drafts with clear rationale during the design phase.