korenko-git/opencode-setup/improve-codebase-architecture

Improve Codebase Architecture

Identify architectural friction that a deeper module could remove. Use the vocabulary in codebase-design: module, interface, depth, seam, adapter, leverage, and locality. Read CONTEXT.md and relevant ADRs when present.

Workflow

1. Explore the relevant area. For a bounded independent survey, use Task

with subagent_type: explore; provide the scope, questions, and required report. Look for shallow modules, leaky seams, poor locality, and interfaces that are difficult to test. Apply the deletion test before recommending a change.

1. Create a self-contained HTML report in the OS temp directory, named

architecture-review-<timestamp>.html, and tell the user its absolute path. Each candidate must include involved files, observed evidence, a proposed deepening, locality and leverage benefits, a before/after visualization, and a Strong, Worth exploring, or Speculative rating. Use the domain terms from CONTEXT.md; flag a real conflict with an ADR.

1. Ask which candidate to explore using question. Do not propose an interface

until the user chooses one. Record domain terminology or an ADR only when the user asks and the decision is durable.

Use HTML-REPORT.md for report construction guidance.