design-solution

Produce docs/specs/<YYYY-MM-DD>-<feature>/design.md: HOW the approved requirements get satisfied. Start from the skill set's templates/design.md — first path that exists: templates/ beside this SKILL.md, else ${CLAUDE_PLUGIN_ROOT}/templates, else ../../../templates. Every heading in it is a REQUIRED slot. The requirements file is your input contract — read it fully first.

Create a todo per step (1, 2, 2b, 3, 4) before starting, and complete them in order — this skill owns its own list, distinct from specify-behavior' upstream and plan-tasks's downstream. Check each off only when its Done when: is met.

Step 1: Context and decisions

Explain in 2–4 paragraphs what exists today, which constraint shapes the approach, and the alternative that constraint rules out. Dispatch a scan subagent to map the touched surface — signatures, data shapes, save/load paths — into a digest file (.skills/<CODE>/scan.md, or .skills/_pending-<slug>/scan.md before CODE), not raw source; pull a specific file into context only when a decision hinges on its exact contents. (No subagents? Read the surface directly, only the parts a decision needs.)

WHEN the user has said they have never read the touched subsystem, name /understand for them to run before treating a scan digest as a traced model. Do not invoke it. The on-ramps table is the one home for that row.