architecture-session

Runs a six-phase architecture decision session producing ADRs and vault updates.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill architecture-session-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-session
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/architecture-session
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill architecture-session-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architecture decisions made in conversation get lost, re-debated, or built on stale assumptions. This Skill enforces a structured, evidence-based session that verifies current project state, audits multiple references before generalizing, and persists every decision as an ADR before the session ends. ## Core Features & Use Cases - Six-phase workflow (A-F): state verification, multi-reference audit (Regla del 3 gate), constraint formalization, options with rejection list, in-session ADR persistence, and recap via handoff/context-refresh skills. - Blocking quality gates: refuses to advance past the audit phase without at least two references for cross-instance decisions, and refuses to end without writing the ADR file. - Socratic option filter: evaluates 3-5 candidate options against a formalized constraint table using invariant checks, naive-trap analysis, falsifiable rejection criteria, and one-way vs two-way door classification. - Use Case: A team must choose a shared SDK template across multiple sensor products. The session audits two-plus reference implementations, formalizes constraints, records the decision as an ADR in the repo's docs/adr directory, and updates the plan and GitHub issues in the same session. ## Quick Start Ask the agent to run an architecture session for your project, for example by saying "run an architecture session to decide the config schema for the sensor SDK platform".

Frequently Asked Questions about architecture-session

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

FAQPage Schema
How do I run an architecture decision session with an AI agent?

Invoke /architecture-session or /arch, or ask in natural language to define or review the architecture of a project. The skill walks through six phases from state verification to ADR persistence, ending with a written ADR in the repo's docs/adr directory.

What is the difference between an architecture session and a spec-driven feature workflow?

Architecture sessions produce ADRs and roadmap decisions at cross-cutting granularity, while /spec init produces implementation plans and code for individual features. Use the architecture session upstream, then /spec init for the feature work the ADR creates.

When should I skip the multi-reference audit phase?

Skip Phase B only when the decision does not affect cross-instance reuse, such as refactoring one internal module or tuning a single repo's CI. Any decision about shared templates, libraries, or generalized configs requires auditing at least two references.

Can I defer writing the ADR to a later session?

No. The skill blocks session completion until the ADR file is written, because decisions left in conversation are lost. If an interruption prevents authoring, it creates a tracked GitHub issue for the ADR draft instead of accepting verbal deferral.

What environment setup does the architecture session require?

It requires a resolvable VAULT_PATH via environment variable, the dotf CLI, or machine.json config, plus access to the project area in the vault. Without vault access the session fails fast, since its output is persisted decisions.