architect-mode

Guide architecture design through a five-phase protocol with scoring rubric.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/veegee82/loss-driven-development --skill architect-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-mode
Source: https://github.com/veegee82/loss-driven-development/tree/main/skills/architect-mode
Command: npx skills add https://github.com/veegee82/loss-driven-development --skill architect-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architect-mode provides a disciplined framework to explicitly define constraints, non-goals, and evaluation criteria before designing a software architecture, reducing scope creep and ensuring traceable decisions.

Core Features & Use Cases

  • A rigid 5-phase protocol (Constraint extraction, Non-goals declaration, Three candidate designs, Scoring, Deliverable).
  • Formal deliverables: architecture doc + initial scaffold + contracts, all within a single commit.
  • Ideal for greenfield projects or when a deliberate redesign requires clear trade-offs and validation plans.

Quick Start

Provide the task objective and constraints, and run architect-mode to generate the architecture doc and initial scaffold.

Frequently Asked Questions about architect-mode

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

FAQPage Schema
How do I design software architecture for a greenfield project with traceable decisions?

Design software architecture for greenfield projects using a disciplined five-phase protocol that extracts constraints, declares non-goals, scores candidate designs, and delivers auditable architecture documentation with initial scaffolding.

What is a structured architecture design protocol and how does it prevent scope creep?

A structured architecture design protocol prevents scope creep by enforcing explicit constraint extraction and non-goals declaration before generating designs, ensuring all architectural decisions remain traceable to original project requirements.

How do I generate architecture documentation and initial project scaffolding together?

Generate architecture documentation and project scaffolding together by running a protocol that produces formal deliverables including contracts, an architecture doc, and an initial scaffold, all verifiable within a single commit.

How do I evaluate and score multiple candidate designs for a software redesign?

Evaluate candidate designs for a software redesign using a formal scoring rubric applied to three distinct architectural options, utilizing dialectical reasoning to validate measurable outcomes and clear trade-offs.

When should I use a formal architecture protocol instead of ad-hoc system design?

Use a formal architecture protocol for deliberate redesigns or greenfield projects where strict structure, measurable outcomes, and defined contracts are required, rather than ad-hoc system design suited for unrestricted exploration.

How do I define non-goals and constraints before creating a software architecture?

Define non-goals and constraints before creating software architecture by applying a constraint extraction phase that explicitly documents boundaries and evaluation criteria prior to generating candidate designs and deliverables.