design-first

Triage tasks to determine whether architecture design is required before implementation.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill design-first-maestria-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-first
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/design-first
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill design-first-maestria-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Not every task requires upfront architecture design; this skill triages tasks to decide design-first vs implement-direct to reduce risk and rework.

Core Features & Use Cases

  • Triage criteria to identify when design-first is necessary, including new subsystems, cross-cutting changes, data-model shifts, or irreversible decisions.
  • Guidance on lightweight design versus full ADR workflows, and when to generate plan.md or ADR artifacts.
  • Step-by-step workflow for starting a task with design considerations, then transitioning to implementation if appropriate.

Quick Start

Analyze the task at hand and reply with a design-first plan if it meets triage criteria; otherwise proceed with direct implementation.

Frequently Asked Questions about design-first

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

FAQPage Schema
When do I need architecture design before implementing a new module?

Architecture design is required before implementing new modules, data model changes, API design, or cross-cutting changes affecting multiple files. Triage criteria identify these irreversible decisions to reduce risk and rework.

What is the best way to decide between upfront design and direct implementation?

The best way to decide between upfront design and direct implementation is applying task triage criteria. Evaluate task scope to determine if new subsystems, data-model shifts, or cross-cutting changes require design-first workflows.

How do I create an ADR for cross-cutting code changes?

To create an ADR for cross-cutting code changes, follow the recommended full ADR workflow and generate artifacts in the .context/decisions/ directory to document irreversible architecture decisions.

Do I need a full architecture design for every API change?

No, you do not need a full architecture design for every API change. Task triage assesses the scope; lightweight design generating a plan.md artifact may suffice for lower-risk API changes.

Why does task triage recommend lightweight design over full ADRs?

Task triage recommends lightweight design over full ADRs to reduce overhead for smaller tasks. It reserves full ADR workflows and .context/decisions/ artifacts for irreversible decisions or cross-cutting changes.

How to start a task with design considerations before coding?

To start a task with design considerations, analyze the task at hand against triage criteria. If it involves new subsystems or data model changes, generate a plan.md before transitioning to implementation.