coding-design-plan

Installation
SKILL.md

Coding Design Plan

Turn one approved task into the smallest coherent shape an implementer can build without making a new product or architecture decision. Choices settled in the PRD or task are already decided; build on them.

Workflow

  1. Read the task, its acceptance contract, and the project's conventions. Inspect the relevant code, tests, and current behavior.
  2. State the design problem in one sentence: the behavior that changes and its owner.
  3. Map only the affected boundary: module, component, service, data store, public contract, or deployment path. Use change ownership to place each responsibility where its next change belongs.
  4. Choose the smallest coherent shape that fits the existing code. When a real alternative exists, state the one trade-off that decides it. When the code makes one local move clear, take it.
  5. Add a check only when its trigger applies:
    • The task crosses a nonlocal boundary and has no lens conclusions yet: run design-gate.
    • The task already carries lens conclusions: apply them as constraints.
    • One uncertainty only running code can answer: use to-prototype. Prototype code never graduates.
  6. Name a test or direct check for every changed behavior. For a nonbehavior change, say why a test does not help and name the replacement check.
  7. Put adjacent work you discover in deferred. Widening scope needs a new task or the user's instruction.

Use a safe default for nonmaterial details and state the assumption. Ask the user only when a fact you cannot inspect would change the shape, public behavior, risk, scope, or cost.

Installs
85
GitHub Stars
2
First Seen
Jun 10, 2026