All notable changes to the AI Software Architect framework will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
tools/npm testworks on bash CI runners. The script wasnode --test test/**/*.test.js— that glob is expanded by zsh on macOS but passed literally on bash, breaking CI. Switched tonode --test(Node 22+ auto-discovers*.test.jsfiles in cwd recursively), making the script shell-agnostic.claude-smokejob no longer asserts on disable-model-invocation skills. The smoke test prompted Claude to "list every skill loaded from this plugin" and asserted all seven appeared. This was wrong:setup-architect,create-adr, andpragmatic-guardare markeddisable-model-invocation: truein 1.5.0 — Claude deliberately excludes them from "list loaded skills" output (they're user-invoked only). SKILL.md presence for all seven is already verified byvalidate-plugin's required-layout check; the smoke now asserts only on the four auto-invocable skills, with an inline comment explaining the partition.
The first live claude-smoke run successfully loaded the plugin and surfaced the four auto-invocable skills, validating ADR-013's orchestrator pattern and ADR-014's plugin source discovery end-to-end. Both failures in the first run were CI infrastructure bugs surfaced by the live test, not framework regressions.
setup-architectnow works correctly on plugin installs. The skill previously instructed users to clone the framework into.architecture/.architecture/even when the plugin was already installed and the templates were on disk under~/.claude/plugins/. The skill now performs deterministic source discovery via the newfind-sourceCLI subcommand, falling back through three sources in order:${CLAUDE_PLUGIN_ROOT}env var →~/.claude/plugins/recursive search →.architecture/.architecture/legacy clone path.
node tools/cli.js find-source— discovers and prints the framework source location. Returns the resolved path on stdout (exit 0) or a dual-option error message (exit 1) directing the user to either/plugin marketplace add codenamev/ai-software-architector the legacygit clonepath. Supports--jsonfor structured output.tools/lib/setup-source-discovery.js— deterministic discovery logic, 12 unit tests covering env var, plugin candidates (in order), legacy clone fallback, and absent-source error path.- CI verifies discovery resolves correctly — the
validate-pluginjob runsfind-sourcewithCLAUDE_PLUGIN_ROOTset to the workspace and asserts it returns the workspace path.
ADR-014 scopes three changes; only Change A ships in 1.5.2. Change B (--dry-run preview) is conditional and will be evaluated based on Change A's smoke-test outcomes. Change C (partial-install recovery) is deferred until triggered by real user reports. See ADR-014 § Pragmatic Enforcer Analysis for the per-change scoring.
A targeted pass through the setup user-journey based on a fresh DevX audit. No behavior changes — purely doc and template clarity. Targets the post-1.4.0 plugin-install path, where the previous docs still described the legacy clone-based flow.
setup-architect/SKILL.mdgained a "What happens when you run this" walkthrough at the top, a "Setup successful when..." checklist users can verify against, and a "Recovery" section for partial installs. The verify-prerequisites step now describes plugin source-discovery alongside the legacy clone path; error messages surface both install options.installation-procedures.mdmarks the.architecture/.architecture/clone-based flow as the traditional path and adds an upfront note about the canonical plugin path.member-template.ymlleads with a single minimum-viable example showing all seven required fields filled, before the stack-specific examples. Adds explicit pointer to the PreToolUse hook so users know how to actually save edits.initial-analysis-template.mdannotates each section as either required for minimum viable analysis or optional on first pass, so first-time users aren't overwhelmed by a 400-line template.USAGE-WITH-CLAUDE-PLUGIN.mdgains a "First 5 minutes after setup" quick-start with four concrete steps that exercise the full plugin (list-members, read analysis, create-adr, specialist-review).
- Reconciled dynamic-specialist-creation references across
USAGE-WITH-CLAUDE.md,README.md, andUSAGE-WITH-CLAUDE-PLUGIN.md. ADR-013 removed auto-creation; the docs now describe the post-1.5.0 reality (editmembers.yml+ override the PreToolUse hook + regenerate). - Dead
INSTALL.mdlink inUSAGE.mdretired (the file never existed); replaced with a pointer to README.md's Installation section. - Stale
USAGE-WITH-CLAUDE-SKILLS.mdreferences inUSAGE.mdandREADME.mdredirected toUSAGE-WITH-CLAUDE-PLUGIN.md, the actual canonical install doc. - Confusing "33% / 60%" feature percentages in
USAGE-WITH-CLAUDE-PLUGIN.md's comparison table replaced with prose noting the Skills install path was retired in 1.4.0.
The DevX audit also identified a P2 candidate — a setup-architect --dry-run mode and resume-from-checkpoint — which is real behavior change and queued for ADR-014. The P0+P1 work shipped in 1.5.1 is corrective + narrative only; no risk of behavior regression.
- PreToolUse hook protects framework source-of-truth files.
.architecture/{members.yml, principles.md, config.yml}now reject Write/Edit operations with a tailored explanation pointing at the correct workflow (regenerator, ADR, pragmatic-guard skill). Override withCLAUDE_ALLOW_PROTECTED=1for intentional one-off edits. Logic intools/lib/protected-files.js(TDD, 11 tests). disable-model-invocation: trueadded to side-effect skills (create-adr,setup-architect,pragmatic-guard). These workflows now require explicit user invocation; the model will not auto-fire on inferred intent.
architecture-reviewandspecialist-reviewnow delegate to subagents. Both skills became orchestrators that dispatchAgent({subagent_type: ...})calls to theagents/*.mdfiles generated in 1.4.0, instead of adopting personas inline. Reviews run in forked subagent contexts, preserving main-thread tokens and eliminating mid-review persona drift. See ADR-013.setup-architectallowed-toolsscoped. Was unscopedBash; nowBash(git:*,npm:*,node:*,mkdir:*,cp:*,ls:*,test:*)— matches what the skill actually runs.create-adrdropsBash(grep:*)in favor of theGrep/Globtools, per the project's own convention.
- Dynamic specialist creation in
specialist-reviewis no longer auto-applied. The previous behavior wrote new members tomembers.ymlon the fly; the new PreToolUse hook makes that an explicit two-step (override the hook, editmembers.yml, regenerate subagents). Trade-off: one-step convenience for stable, drift-free framework source files. See ADR-013 § Pragmatic Analysis.
- Skills relocated to plugin root:
.claude/skills/→skills/. Claude Code plugins load skills fromskills/at the plugin root, so installations via/plugin marketplace addnow correctly receive all seven skills (previously only the MCP server was delivered). - Plugin marketplace install is the canonical Claude Code distribution. The README's installation methods drop from four to three (Plugin / MCP / Traditional); the comparison tables and decision tree are updated accordingly.
- Plugin/marketplace metadata corrected:
homepageandrepositoryURLs inplugin.jsonandmarketplace.jsonnow point tocodenamev/ai-software-architect(previously misconfigured toanthropics/).
- Legacy "Claude Skills" cp-based install path retired. The pre-plugin
git clone … && cp -r .../skills ~/.claude/skills/recipe was a strict subset of plugin installation (skills only, no MCP server, settings, hooks, or subagents).USAGE-WITH-CLAUDE-SKILLS.mdis now a redirect pointing atUSAGE-WITH-CLAUDE-PLUGIN.md.
If you previously installed via the cp recipe, install the plugin instead:
/plugin marketplace add codenamev/ai-software-architect
/plugin install ai-software-architect@ai-software-architectOptionally clean up the manually-copied directories under ~/.claude/skills/. No changes are required for users who installed via the plugin or MCP server.
- Implementation Strategist: New architecture team member focused on HOW and WHEN (blast radius analysis, reversibility design, team readiness assessment, change sequencing)
- Change Impact Awareness Principle: New Principle #8 systematically captures blast radius, reversibility, timing, social cost, and false confidence detection
- Senior Thinking Checklist: Enhanced review template with framing questions that externalize the "silent checklist" senior engineers use
- Implementation Strategy Section: Enhanced ADR template with systematic impact analysis (blast radius, reversibility, sequencing & timing, social cost, confidence assessment)
- Strategic Framework Positioning: Framework now explicitly creates the "missing corpus" of senior architectural thinking identified by industry thought leaders
- Knowledge Capture: Systematically documents invisible architectural reasoning that typically stays undocumented
- Progressive Disclosure Compliance: All enhancements maintain instruction capacity constraints (ADR-005, ADR-006, ADR-008)
- Auto-Discovery: Implementation Strategist automatically available in Skills, MCP server, and all integration points via dynamic member loading
- Architecture Team: Expanded from 7 to 8 core members with Implementation Strategist
- Architectural Principles: Enhanced from 7 to 8 principles with Change Impact Awareness
- Review Process: Review template now includes Senior Thinking Checklist for comprehensive impact framing
- ADR Process: ADR template now requires Implementation Strategy analysis before implementation
- Directory Structure: Added
agent_docs/to standard structure (progressive disclosure pattern)
- ADR-010: Externalizing Senior Engineering Thinking - Documents strategic value and positions framework as solving industry gap
- Referenced Work: Obie Fernandez - "What happens when the coding becomes the least interesting part of the work" (2025)
- README: Updated to reflect Implementation Strategist, senior thinking capture, and agent_docs/ directory
New Team Member:
implementation_strategist:
specialties:
- change sequencing
- blast radius analysis
- reversibility design
- team readiness assessment
perspective: "Evaluates HOW and WHEN changes should be implemented"Enhanced Templates:
- Review template: +100 lines (Senior Thinking Checklist)
- ADR template: +119 lines (Implementation Strategy section)
- Principles: +38 lines (Principle #8)
Statistics:
- 5 files modified, 486 lines added
- 1 new ADR created (ADR-010)
- Framework positioned as strategic knowledge capture system
- Cross-Platform AI Assistant Support: Added
AGENTS.mdas universal entry point for all AI assistants (Claude, Cursor, Copilot, Jules, etc.) - Template System: Created
.architecture/templates/AGENTS.mdfor project-specific generation during setup - Multi-Assistant Architecture: Framework now works seamlessly across 20,000+ projects using the Agents.md standard
- Complementary Documentation:
AGENTS.mdprovides cross-platform instructions whileCLAUDE.mdadds Claude Code-specific enhancements
- Configuration-Driven Implementation: Specify methodology, influences, and practices once in
.architecture/config.yml - Simple Command Pattern: Use "Implement X as the architects" instead of 40+ word prompts (90% reduction)
- Methodology Support: TDD, BDD, DDD, Test-Last, Exploratory development approaches
- Coding Influences: Configure thought leaders (Kent Beck, Sandi Metz, Martin Fowler, Gary Bernhardt, Jeremy Evans, Vladimir Dementyev)
- Language-Specific Practices: Per-language style guides, idioms, and framework conventions
- Security-First: Security practices always applied, exempt from YAGNI challenges
- Quality Standards: Configurable definition of done, refactoring guidelines, testing approach
- MCP Server: Added
get_implementation_guidancetool for programmatic access to implementation configuration - Claude Code: Full implementation command recognition with methodology application
- Codex: Setup instructions with implementation guidance and examples
- Cursor: README documentation with configuration and usage patterns
- Claude Skills: Updated
setup-architectskill to include implementation commands
- MCP Tool: Added
pragmatic_enforcertool to MCP server for programmatic YAGNI analysis - Automated Complexity Assessment: Scores necessity (0-10) and complexity (0-10) with ratio analysis
- Simpler Alternatives: Always proposes concrete simpler approaches
- Deferral Recommendations: Tracks what can be implemented later with trigger conditions
- Framework Version: Bumped from 1.1.0 to 1.2.0
- MCP Server Version: Bumped from 1.1.0 to 1.2.0
- Documentation Structure: Clarified relationship between AGENTS.md (cross-platform) and CLAUDE.md (Claude-specific)
- Config Template: Expanded
.architecture/templates/config.ymlwith implementation section (+175 lines) - Setup Process: Framework setup now generates project-specific AGENTS.md from template
- ADR-003: Agents.md Standard Adoption - Full decision record with alternatives analysis
- ADR-004: Implementation Command with Configuration - Comprehensive decision record with pragmatic assessment
- Architecture Reviews:
feature-agents-md-adoption.md- Multi-perspective review of Agents.md adoptionfeature-implementation-command-configuration.md- 7-member collaborative review
- AGENTS.md: 518 lines documenting framework for all AI assistants
- Implementation Examples: Ruby TDD, JavaScript BDD, Python Test-Last configurations
- Update Command Clarity: Added full GitHub URL to update instructions to avoid ambiguity
- Cross-Platform Consistency: Ensured all integration methods have equivalent implementation feature documentation
Implementation Configuration Structure:
implementation:
enabled: true
methodology: "TDD" # or BDD, DDD, Test-Last, Exploratory
influences:
- "Kent Beck - TDD by Example"
- "Sandi Metz - POODR, 99 Bottles"
- "Martin Fowler - Refactoring"
languages:
ruby:
style_guide: "Rubocop"
idioms: "Blocks over loops, meaningful names"
quality:
definition_of_done:
- "Tests passing"
- "Code refactored"MCP Server New Tools:
get_implementation_guidance(projectPath, featureDescription?)- Returns formatted implementation guidancepragmatic_enforcer(recommendation, context, mode?)- Analyzes recommendations for YAGNI compliance
Statistics:
- 8 files modified, 2,886 lines added
- 2 new ADRs created
- 2 comprehensive architecture reviews conducted
- 5 integration methods fully documented
- Claude Skills conversion for all architecture operations
- Pragmatic Guard Mode configuration and behavior
- Initial MCP server implementation with core tools
- Cross-assistant configuration directories
- Converted to Skills-based architecture for Claude Code
- Enhanced members.yml with Pragmatic Enforcer role
- Improved setup process with project-specific customization
- Initial framework release
- Architecture Decision Records (ADRs) system
- Architecture reviews with multi-perspective analysis
- Architecture recalibration process
- Members system with specialized roles
- Principles-based architectural guidance
- Template system for ADRs and reviews
- Claude Code integration
- CLAUDE.md for Claude Code usage
- USAGE-WITH-CLAUDE.md comprehensive guide
- Installation and setup instructions
- Example ADRs and reviews
See AGENTS.md for guidelines on contributing to the framework.