skills.rest
repowise-dev
repowise-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

architectural-decisions

Identify and surface rationale behind architectural decisions from code, commits, and docs.

5.0k|548|Updated Mar 23, 2026
Search Tags:#architecture#documentation#decisions#codebase#architectural#design-rationale#get_why
One-click install
npx skills add https://github.com/repowise-dev/repowise --skill architectural-decisions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architectural-decisions
Source: https://github.com/repowise-dev/repowise/tree/main/plugins/claude-code/skills/architectural-decisions
Command: npx skills add https://github.com/repowise-dev/repowise --skill architectural-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams understand the rationale behind architectural decisions in a Repowise-indexed codebase. It surfaces and organizes why certain design choices were made, by aggregating decision markers from code comments (WHY:, DECISION:, TRADEOFF:, ADR:), commit history, and documentation, so teams can reason about changes and maintain consistency.

Core Features & Use Cases

  • Surface existing decisions for a given area using get_why to surface rationale from code, commits, and docs.
  • Review and audit architectural decisions before making changes to ensure alignment with prior reasoning.
  • Monitor decision health and hotspots with a dashboard-like view to identify ungoverned areas.
  • Record new decisions by adding standardized markers or using dedicated tooling (e.g., repowise decision add).

Quick Start

Call get_why(query="the area you're changing") to surface existing decisions relevant to that area.

Frequently Asked Questions about architectural-decisions

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

FAQPage Schema
How do I find the rationale behind architectural decisions in a codebase?▼

To find architectural rationale, use the get_why query to surface design decisions extracted from code comments, commit history, and documentation. This aggregates WHY, DECISION, and TRADEOFF markers to help you reason about system structure and maintain consistency.

How do I document architectural design decisions and tradeoffs in my code?▼

Document architectural decisions by adding standardized markers like WHY:, DECISION:, TRADEOFF:, or ADR: directly in code comments, or use dedicated tooling such as repowise decision add to record new design rationale across indexed modules.

Can I audit existing architectural decisions before making code changes?▼

Yes, you can audit architectural decisions before changing code by calling get_why with your target area. This surfaces prior reasoning and decision records, ensuring your proposed changes align with existing structural patterns and documented tradeoffs.

What is the best way to monitor architectural decision health and find ungoverned areas?▼

Monitor architectural decision health by using the dashboard-like view to identify hotspots and ungoverned areas. This surfaces regions lacking documented rationale, helping teams target where new ADR or DECISION markers are needed.

Does this architectural decision tracing require a specific codebase indexing setup?▼

Yes, architectural decision tracing requires a Repowise-indexed codebase. The tooling aggregates decision markers, commit history, and documentation from the indexed repository to surface rationale and support querying existing design choices.

Related Skills

Explore More Software Engineering Skills→
MisterVitoProMisterVitoPro

code-atlas:map

Scan a codebase to generate atlas.json and state.json architecture indexes.

Community
Intermediate
Prompt-or-Die-LabsPrompt-or-Die-Labs
7

architecture-decision-recorder

Capture architectural decisions and rationale in standardized ADR documents.

Official
Basic
oto1720oto1720
1

tech-architecture-diagram

Generate Mermaid, HTML, and SVG architecture diagrams from repository structure and dependencies.

Community
Advanced
Euraika-LabsEuraika-Labs
14

architecture-decision

Create Architecture Decision Records with required sections for game development projects.

Official
Advanced