seemseam Archi Advice
Use this skill to turn architecture evidence into an actionable improvement plan.
Workflow
- Establish a full-project baseline unless a fresh baseline already exists and is clearly relevant.
- If active changes matter, also inspect change-scoped architecture evidence.
- Use
archi-evidence-mapwhen selecting optional tools or when Architec is unavailable. - Use vendored
improve-codebase-architecturewhen advice should identify deepening opportunities or compare interface shapes. - Use vendored
receiving-code-reviewwhen advice is based on external review feedback that needs verification before action. - Use focused method skills when advice depends on topology, boundaries, fitness functions, decision drift, change impact, or distributed systems.
- Read the human summary before raw structured output when tool artifacts exist.
- Inspect relevant source files directly before recommending changes.
- Convert findings into phased work.
Output
Current Position
- baseline score:
- current reading:
Immediate
- ...
Next
- ...
Later
- ...
Validation
- ...
Advice must be grounded in evidence. Do not produce a roadmap from diff context alone when the user is asking about long-term architecture. If no tool evidence exists, ground the roadmap in source inspection, module docs, tests, and explicit residual risk.