vp-s07-architecture-decisions

Analyze codebases to surface implicit Architecture Decision Records with rationale and alternatives.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/velesar/alpha-zero-review- --skill vp-s07-architecture-decisions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vp-s07-architecture-decisions
Source: https://github.com/velesar/alpha-zero-review-/tree/main/skills/vp-s07-architecture-decisions
Command: npx skills add https://github.com/velesar/alpha-zero-review- --skill vp-s07-architecture-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover implicit Architecture Decision Records (ADRs) by analyzing code patterns, decision traces, and rationale that are not explicitly documented, enabling traceable architectural reasoning.

Core Features & Use Cases

  • Discover implicit architectural decisions by pattern analysis and hotspot detection across modules.
  • Extract and organize related ADRs and rationale, including alternatives and trade-offs.
  • Update the mental model with detected decisions and document context for future audits.

Quick Start

Load the VP-S07 viewpoint, run pattern discovery, and export the inferred ADRs for review.

Frequently Asked Questions about vp-s07-architecture-decisions

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

FAQPage Schema
How do I discover implicit architecture decisions in a codebase?

Discover implicit architecture decisions by analyzing code patterns, decision traces, and module hotspots to surface undocumented ADRs with rationale and alternatives. The Skill extracts these implicit choices to provide traceable architectural reasoning across the codebase.

What is an implicit ADR and how does code analysis find it?

An implicit ADR is an architectural choice embedded in code patterns rather than explicit documentation. Code analysis locates these decisions by evaluating structural patterns, trace hotspots, and dependency impacts across modules to extract the underlying rationale.

Do I need SCIP indexes and codegraph analysis to document architectural rationale?

SCIP indexes and codegraph analysis are utilized to assess structural patterns, locate hotspots, and evaluate impact across modules. They support extracting architectural decisions and documenting the context, rationale, and alternatives for future audits.

How do I extract and organize ADRs from existing code patterns?

Extract and organize ADRs by running pattern discovery across modules to identify decision traces. The process surfaces both explicit and implicit architectural logic, organizing the detected decisions with their corresponding rationale, trade-offs, and alternatives.

What's the best way to update a mental model with detected architectural decisions?

Update the mental model with detected architectural decisions by exporting inferred ADRs after pattern discovery. This documents the architectural context, rationale, and alternatives within the mental-model service, enabling traceable reasoning for future audits.