Execute

→ Have an existing parent plan/spec and a tiny execution slice? → Use Planless Slice Lane.

Emit a compact Slice Card: goal, parent plan/spec, files, boundary, verification, stop
Update the parent workstream checkpoint/evidence/drift state if persistent state is needed
Do not save a new plan for the micro-slice → Have approved spec/requirements for a new workstream or an escalation trigger? → Write implementation plan. Assume engineer has zero context.
Scope check: fact/assumption/unknown, baseline, Requirement Ready Check, Ripple Signal Triage, compatibility boundary, dual-track needs
File map: what files created/modified, clear boundaries, follow existing patterns
Bite-sized tasks (2-5 min each): exact file paths, complete code, exact commands, expected output
Self-review: spec coverage, placeholders, type consistency, compatibility, verification, dual-track
Save → offer execution choice (subagent-driven or inline) → Plan must answer: problem, baseline, files, compat, verification, risks, retirement. → Escalate from Planless Slice Lane to a durable plan when the slice adds a new owner, contract, schema, public API, architecture boundary, migration, persistence, security/permission, distribution/release surface, or unclear verification boundary.

writing-plans