writing-plans

1<EXPLICIT-MODE-GATE>
2If activation mode is explicit (`~/.config/aegis/config.toml` has
3`activation_mode = "explicit"`, or `AEGIS_ACTIVATION_MODE=explicit` is visible
4in the environment) and the current user request did not explicitly invoke
5Aegis or this skill by name, exit back to the fast path: answer concisely
6without this workflow's checklist, ceremony, or document requirements. If the
7user explicitly named Aegis or this skill, proceed normally.
8</EXPLICIT-MODE-GATE>
9 
10# Execute
11 
12→ Existing parent plan/spec and a tiny execution slice? → **Use Planless Slice Lane.**
13→ Mechanical or bounded change with no durable boundary (no new owner,
14  contract, schema, public API, migration, or compat surface)? → **Use
15  Planless Slice Lane without a parent document.**
16→ Approved spec/requirements for a new workstream or an escalation trigger? →
17  **Write an implementation plan for an engineer with no prior task context.**
18 
19For a durable plan: confirm scope and acceptance, map current owners/files,
20record the TDD route, decompose into executable tasks, define verification and
21retirement, self-review, save, then select the execution route. Proceed unless
22a real authorization or safety boundary requires the user.
23 
24Bind tasks to the requested user outcomes: object, actions, conditions, and
25deliverables. Include the final delivery step and evidence at the user-visible
26seam, not only implementation/tests. Keep unmet needs and dependencies explicit;
27…