2026-10-13 16:45:12 +08:00
|
|
|
---
|
|
|
|
|
name: deepen
|
|
|
|
|
description: >
|
2026-10-30 12:40:16 +08:00
|
|
|
Simplify module interfaces while preserving behavior when asked to deepen modules, improve their design, or hide leaked implementation decisions.
|
|
|
|
|
scope: global
|
2026-10-13 16:45:12 +08:00
|
|
|
---
|
|
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
# Deepen a module
|
2026-10-13 16:45:12 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
1. Inspect the target module, callers, and existing behavior checks. Identify the
|
|
|
|
|
concrete complexity exposed to callers with file/line evidence.
|
|
|
|
|
2. Choose the smallest interface improvement that hides a real decision. Keep
|
|
|
|
|
existing behavior and contracts unless the user authorized changing them.
|
|
|
|
|
3. Refactor the selected boundary without unrelated cleanup or speculative layers.
|
|
|
|
|
Update an existing spec only if its contract is affected; do not require a spec.
|
|
|
|
|
4. Verify affected behavior under [shared verification](../../protocols/workflow.md#verification).
|
|
|
|
|
Distinguish pre-existing failures from regressions rather than requiring the
|
|
|
|
|
entire repository to be green before starting.
|
|
|
|
|
5. Show the interface change, complexity hidden, and verification result.
|
2026-10-13 16:45:12 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
Do not activate merely because token budget remains. Improve the requested scope;
|
|
|
|
|
keep dependent changes coherent rather than imposing an arbitrary one-module limit.
|
