matched-abstraction

Use when design, planning, implementation, or delegation risks mixing abstraction layers or skipping from high-level intent to detail too quickly; triggers include architecture decisions, design artifacts, testing strategy, implementation plans, task handoffs, layered docs, orchestration, decomposition, verification strategy, artifact-set refinement, derive/match review surfaces, and strategy-to-execution drift.

Use when design, planning, implementation, or delegation risks mixing abstraction layers or skipping from high-level intent to detail too quickly; triggers include architecture decisions, design artifacts, testing strategy, implementation plans, task handoffs, layered docs, orchestration, decomposition, verification strategy, artifact-set refinement, derive/match review surfaces, and strategy-to-execution drift.