design-codebaselisted

# Design Codebase ## Purpose and authority Decide what the target design is and why it is the right structural choice. Inspect the repository without editing implementation files. Produce one validated `design-handoff.md` for `plan-change`. Stop at design. Never classify implementation tier, perform a full propagation sweep, prescribe file-level edits, write test or execution blueprints, order migrations or rollout, or attack an implementation. Those responsibilities belong to `plan-change`. Paths are evidence locators, not edit instructions. ## Start Resolve `skill-root` to this directory and pass absolute repository, draft, and output paths: ```bash python /absolute/skill-root/scripts/cli.py --repo-root /absolute/repo \ --input draft=/absolute/draft.md \ --input output_dir=/absolute/output --format json run ``` Run each returned `next_command.argv` with its returned `cwd`. Read only the current `required_reads`, write only `allowed_writes`, and stop on every `blocking_reason`. ## Next-step loop 1. Follow the seven completion gates in [Design Protocol](references/design-protocol.md). 2. Use [Bounded Delegation Protocol](references/delegation-protocol.md) for optional read-only review; the primary retains authority. 3. Draft the exact eight-section shape in [Handoff Template](references/handoff-template.md). 4. Use [Worked Example](references/worked-examples.md) only when structural-alternative or interface-contract calibration is needed. 5. Run the stateless `ru