architecture

Facilitate Architectural Decision Records and trade-off analysis for design choices.

45|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rakovi4/continue-framework --skill architecture-rakovi4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/rakovi4/continue-framework --skill architecture-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of navigating architectural decisions by facilitating structured discussion, trade-off analysis, and documentation. It helps when encountering multiple design choices and requires a methodical approach before coding continues.

Core Features & Use Cases

  • Architectural Decision Documentation: Enables the creation of Architectural Decision Records (ADR) for structured documentation.
  • Interactive Decision-Making: Facilitates a dialogue between the developer and AI to explore multiple design options and their trade-offs.
  • Code-Free Environment: Ensures that code generation is paused during the decision-making process to maintain focus on planning.

Quick Start

/architecture 5 "task ordering within columns" # Initiate an ADR for a specific decision.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I document architectural decisions and analyze design trade-offs?▼

You can document architectural decisions by creating Architectural Decision Records (ADRs) to structure discussions and analyze design trade-offs methodically before coding continues.

What is the best way to structure architectural discussions before implementation?▼

The best way to structure architectural discussions is through an interactive dialogue that explores multiple design options and their trade-offs within a code-free environment to maintain planning focus.

When do I need to create an Architectural Decision Record?▼

You need to create an Architectural Decision Record when encountering multiple design choices and requiring a methodical approach to evaluate trade-offs before proceeding with code implementation.

What context do I need to provide for architectural decision-making?▼

You need to provide story context, current progress, relevant code, test specs, and existing ADRs as input to generate accurate ADR content and update test specifications.

Can I generate code while evaluating architectural design options?▼

No, code generation is paused during the architectural decision-making process to ensure the focus remains entirely on planning, trade-off analysis, and structured documentation.