Design codebase

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 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:

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.
2. Use Bounded Delegation Protocol for optional read-only review; the primary retains authority.
3. Draft the exact eight-section shape in Handoff Template.
4. Use Worked Example only when structural-alternative or interface-contract calibration is needed.
5. Run the stateless run command once to seal the draft; it validates, backfills local evidence hashes, and writes the single handoff atomically.

Keep claims grounded in current evidence. Compare genuinely different boundaries or ownership models, define caller-visible signatures, defaults, nullability, and errors, and leave only planner-owned grounding questions. Use the protocol's shared vocabulary only where it sharpens the decision.

Completion and recovery

Complete only when phase complete returns exactly /absolute/output/handoff.md, evidence verification passes, and no other primary artifact exists. Pass that file to plan-change as request_file; the planning agent writes the separate v6 draft after native exploration and seals both inputs with the stateless run.

If sealing fails, repair the draft named by the diagnostic and rerun the same seal command. If repository evidence changed, refresh the affected evidence before retrying. Never edit a validated draft or hand off an unverified document.