develop

# Develop Run linear implementation with strict gates. ## Input Schema ```json { "goal": "required implementation objective", "mode": "feature|fix|refactor|config|spike", "constraints": [ "optional constraints" ], "done_when": "required acceptance statement" } ``` ## Workflow (Exact Commands) ### 01: Create run directory Run `python PLUGIN_ROOT/shared/create_run.py --skill develop` once. Retain its single printed path as `<run-directory>` and substitute that literal path into every later artifact path and helper argument. Never store or reuse the path through a shell variable; shell variables do not persist across tool calls. ### 02: Record baseline diff and branch Run `git rev-parse --abbrev-ref HEAD` as an argv command and write stdout to `<run-directory>/branch.txt`. Inspect `python PLUGIN_ROOT/shared/collect_diff.py --help`; collect `working-tree` into `<run-directory>/baseline`. ### 03: Route the change type and define ownership Modes: - `feature`: define public behavior, acceptance checks, docs impact, and tests before implementation. - `fix`: reproduce or cite the failing behavior before editing. - `refactor`: preserve behavior with characterization tests or an equivalent safety net. - `config`: inventory references and calibration/routing impact before editing. - `spike`: read-only or disposable probe; do not present as completed implementation. Define narrowest reversible change, owners, acceptance. For 3+ steps/design tradeoffs, update pla...