1.2 KiB
name, description, disable-model-invocation, metadata
| name | description | disable-model-invocation | metadata | ||||
|---|---|---|---|---|---|---|---|
| improve-codebase-architecture | Assess assigned module-deepening opportunities as read-only planning options with evidence and tradeoffs. | true |
|
Architecture opportunity assessment
Use when the planning assignment asks for a bounded architecture assessment. Read the target's domain vocabulary, applicable decisions, and relevant source. Identify where an interface exposes too much complexity, where behavior that changes together has been scattered, or where a module seam makes verification difficult. Apply the deletion test: would removing an apparent abstraction concentrate complexity rather than merely move it?
For each candidate, cite the affected files, current friction, proposed responsibility boundary, effect on locality and test seams, conflict with any existing decision, and a confidence level. Prefer recently active or explicitly named areas. Present options in the planning response and leave unresolved interface choices explicit. Do not spawn exploration agents, generate or open an HTML report, edit domain documents, or initiate a follow-up interview; the owner governs those activities.