evolution-architecture-review
Multi-agent architecture evolvability review for this repository. Use when the user wants to analyze current architecture quality, evolvability, fitness functions, coupling, boundary clarity, delivery flow, or phased evolution strategy. Designed to be invoked from Claude Code with prompts like `/evolution-architecture-review analyze the current architecture evolvability`.
Best use case
evolution-architecture-review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Multi-agent architecture evolvability review for this repository. Use when the user wants to analyze current architecture quality, evolvability, fitness functions, coupling, boundary clarity, delivery flow, or phased evolution strategy. Designed to be invoked from Claude Code with prompts like `/evolution-architecture-review analyze the current architecture evolvability`.
Teams using evolution-architecture-review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/evolution-architecture-review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How evolution-architecture-review Compares
| Feature / Agent | evolution-architecture-review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Multi-agent architecture evolvability review for this repository. Use when the user wants to analyze current architecture quality, evolvability, fitness functions, coupling, boundary clarity, delivery flow, or phased evolution strategy. Designed to be invoked from Claude Code with prompts like `/evolution-architecture-review analyze the current architecture evolvability`.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
## Goal Assess how safely this codebase can evolve, using parallel analysis where possible. Do not give generic architecture advice. Ground every conclusion in repository evidence. Default to read-only analysis. Do not edit code unless the user explicitly changes the task from review to implementation. ## Default Mode Prefer a 4-lens review in parallel. If subagents or `Task` are available, use them. If not, run the same lenses sequentially yourself. ### Lens 1: System shape and boundaries - Identify major modules, ownership boundaries, and dependency direction. - Look for hidden coupling, duplicated semantics, and unclear seams. ### Lens 2: Runtime flow and operability - Inspect task flow, orchestration, state transitions, control-plane behavior, and failure visibility. - Focus on whether the system is observable and debuggable during change. ### Lens 3: Fitness and verification - Inspect hard gates, tests, contract checks, parity checks, and evidence loops. - Determine whether the architecture has executable constraints or mostly human judgment. ### Lens 4: Evolution path - Propose incremental change steps, rollback-friendly sequencing, and smallest viable improvements. - Avoid rewrite-first recommendations. ## Starting Points Read these first unless the user narrows scope: - `AGENTS.md` - `docs/ARCHITECTURE.md` - `docs/product-specs/FEATURE_TREE.md` - `docs/fitness/README.md` - `docs/blog/routa-kanban-agent-team-management.md` - `docs/blog/harness-fitness-function.md` - `src/core/orchestration/` - `src/core/kanban/` - `src/core/specialists/` - `crates/routa-core/src/workflow/` - `crates/routa-server/src/` Then expand only where evidence requires it. ## Scope Hygiene Treat the main repository tree as authoritative. Unless the user explicitly asks otherwise, ignore duplicate or generated trees such as: - `.worktrees/` - `.routa/repos/` - `node_modules/` - `.next/` - `target/` - `out/` - `dist/` - `coverage/` - `tmp/` - `test-results/` When using `Glob`, `Grep`, or `Task`, state these exclusions explicitly so subagents do not waste time or cite mirrored files. ## Workflow 1. Restate the requested architecture scope in one sentence. 2. Gather repository evidence before judging. 3. Establish path exclusions before broad searches. 4. Run the 4 review lenses in parallel if possible. 5. Merge overlapping findings and remove weak claims. 6. De-duplicate mirrored file references and prefer canonical paths. 7. Produce a final report with measurable evolution advice. ## Required Output Use this structure: ```markdown # Architecture Evolvability Review ## Scope ## Current Architecture Snapshot - Facts ## Strengths - ... ## Evolvability Risks - Severity: High/Medium/Low - Evidence: file paths, modules, flows, or checks - Why it slows or endangers evolution ## Fitness Function Gaps - Missing or weak executable constraints - Suggested hard gates or warning checks ## Recommended Evolution Path 1. ... 2. ... 3. ... ## Quick Wins - Small, low-risk improvements ## Open Questions - ... ``` ## Hard Rules 1. Cite concrete files, modules, workflows, or checks for every substantive claim. 2. Prefer evidence from current code over aspirational docs when they conflict. 3. Distinguish facts, inferences, and recommendations. 4. Recommend phased evolution, not aesthetic rewrites. 5. Call out where architecture already has strong fitness discipline. 6. Suggest fitness functions in executable terms whenever possible. 7. Prefer canonical file paths from the main working tree. Do not cite mirrored or generated paths unless necessary. ## Example Invocation ```bash claude -p "/evolution-architecture-review Analyze the current architecture evolvability of this repository." ```
Related Skills
spreadsheets
Use this skill for spreadsheet creation, editing, analysis, formatting, formula modeling, charting, or workbook review. Triggers include requests to create or modify an .xlsx file, build a model or tracker, format a workbook, add formulas or charts, or prepare a shareable spreadsheet deliverable.
slide
Use this skill as reference material when creating or editing presentation slide decks.
Use this skill for PDF generation, conversion, inspection, extraction, editing, form filling, OCR, redaction, or render comparison. Triggers include requests to create a PDF, convert Markdown or HTML or LaTeX or DOCX or PPTX to PDF, extract text or tables or images, fill or inspect forms, OCR scans, compare revisions, or redact content.
docx
Use this skill for creating, editing, and reviewing DOCX files, including generation, formatting, content controls, tracked changes, comments, accessibility checks, redaction, rendering, and diff-based QA workflows.
pr-verify
Comprehensive PR verification skill. Analyzes PR body requirements, reviews comments, checks CI status, and performs E2E testing. Use when a PR is ready for final verification before merge.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
issue-garbage-collector
Two-phase cleanup of duplicate and outdated issue files in docs/issues/. Phase 1 uses Python script for fast pattern matching. Phase 2 uses claude -p for semantic analysis on suspects only.
issue-enricher
Transforms rough requirements into well-structured GitHub issues. Use when the user provides a vague idea, feature request, or problem description and wants to create a GitHub issue. Analyzes codebase, explores solution approaches, researches relevant libraries, and generates actionable issues using `gh` CLI.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.