the-approach

Design or critique system-level architectures with structured interviews and reviews.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/adriaanmostert1976-lab/adriaan-toolkits --skill the-approach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-approach
Source: https://github.com/adriaanmostert1976-lab/adriaan-toolkits/tree/main/business-solution-toolkit/skills/the-approach
Command: npx skills add https://github.com/adriaanmostert1976-lab/adriaan-toolkits --skill the-approach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The 'the-approach' Skill addresses the challenge of designing or critiquing system-level architectures, ensuring clear decision-making and minimizing architecture pain caused by implicit decisions.

Core Features & Use Cases

  • Structured Interviews: Guides through structured questions to draft architecture from scratch.
  • Critical Review: Critiques existing proposals, highlighting weak boundaries, hidden dependencies, and missing trade-offs.
  • Revision Support: Helps design structural changes to existing systems, capturing baseline and migration paths.
  • Use Case: When you need to decide on the shape of a solution, pressure-test a design, or produce a System Design Document.

Quick Start

Trigger the 'the-approach' Skill by asking, "How should this work?" or "Review this design."

Frequently Asked Questions about the-approach

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

FAQPage Schema
How do I design system architecture from scratch using structured interviews?

System architecture design from scratch uses structured interviews to guide targeted questions, defining boundaries, components, and integration points. Input requirements artefacts to yield a baseline design capturing explicit decision rationale and trade-offs.

What is the best way to critique an existing architecture proposal?

Critiquing an architecture proposal involves evaluating boundaries, components, and integration points to highlight weak borders, hidden dependencies, and missing trade-offs. This review process ensures explicit decision rationale and minimizes architecture pain.

How do I plan structural changes and migration paths for an existing system?

Plan structural changes by capturing the existing baseline architecture and defining target boundaries. Revision support helps design the migration path, ensuring component integration points and trade-offs are documented for effective change management.

When do I need a formal system design document for my project?

You need a formal system design document when deciding on the shape of a solution, pressure-testing a design, or ensuring clear decision-making. It minimizes architecture pain caused by implicit decisions and captures explicit trade-offs.

What inputs are required to start an architecture review process?

The architecture review process requires input artefacts like requirements documents or architecture proposals. Providing these inputs allows the review to effectively evaluate boundaries, dependencies, and integration points.