| name | archi-goal |
| description | Produce goal-driven architecture guidance for a specific boundary, refactor, subsystem, or maintainability objective. |
Archi Goal
Use this skill when the user gives a specific architecture objective.
Workflow
- Restate the goal as an architecture constraint.
- Identify the relevant modules, ownership boundaries, and runtime contracts.
- Use
archi-evidence-map to choose direct source review, generated
architecture artifacts, dependency rules, architecture tests, or static
analysis evidence.
- Route the goal through focused method skills when needed: topology,
boundaries, fitness functions, decision drift, change impact, or distributed
systems.
- Use full-project evidence when the goal depends on whole-project structure.
- Use diff evidence when the goal is about an active patch.
- Use vendored
improve-codebase-architecture for refactor goals involving
shallow modules, interfaces, seams, adapters, leverage, or locality.
- Read targeted source files directly.
- Return a staged plan with gates.
Output
Goal
- ...
Relevant Boundaries
- ...
Plan
1. ...
2. ...
3. ...
Risks
- ...
Gates
- ...
Keep the plan practical. Prefer preserving current working behavior over broad
rewrites.
