Plan Format
Intent
- Goal: Exactly one IDSD plan (ICE + Method) for the requested outcome, small or large, from
assets/plan-template.md. - Limits: Only the plan file may change; never edit production code, stage, commit, or push during planning.
Deliveryauthorizes later execution only. - Fails if: an ICE field (
Goal,Limits,Fails if,Reads,Never reads,Persona,Scope,Scenarios,Done means,Quality needs) orMethod→Approach,Work groups,Execution guidanceis missing (the plan is not ready:BLOCK); a plan is overwritten implicitly; delivery is inferred.
Context
- Reads: the planner's evidence,
oc-routingfor skill names, the exact destination path. - Never reads: implementation skill bodies.
- Persona: precise plan author writing for a human and an executor.
- Scope:
oc-plan-deep,oc-plan-light,oc-grillplan mode, and planless SDDrun.mdcontracts.
Expectations
- Scenarios:
- WHEN the destination exists THEN update it only when the user supplied its exact path or the active conversation created or selected it; otherwise ask one closed choice: reuse the existing plan or generate a new slug.
- WHEN the user states explicit delivery intent THEN write one
Delivery:line immediately after the title: no commitsworking-tree, commitscommit-per-unit, TCRtcr; otherwise omit it (execution defaults toworking-tree). Never infer delivery from a PR request, route, work group, or skill name. - WHEN delivery requests are contradictory, duplicated, or unknown THEN block plan creation until resolved.
- WHEN canonical specs matter THEN qualify scenarios as
<capability>/<requirement>with observableWHENandTHEN.
- Done means:
- One file holds every template section; empty optional content is
none, never filler. - Every claim cites
path:lineor is markedhypothesis/open question. - Ordered work groups each have
Files:,Skills:(names fromoc-routingornone, never paths), and acyclicDepends on:. Delivery skills (oc-tcr,oc-commits, other Git skills) never appear in work groups. - Tasks are actionable and verifiable; behavior changes live in
Scenarios, not hidden in tasks. Risks and open questionsholds only real rollback conditions or hazards.Execution guidancegivesRoute: direct | SDD,Reason:, andRun: `ejecuta el plan <path>`.
- One file holds every template section; empty optional content is
- Quality needs: short complete English sentences; paths, symbols, commands, URLs, numbers, and Markdown exact; no cryptic A2A fragments. SDD verification counts every scenario and every
Done meansitem.
Method
Former section mapping: Outcome → Goal; Scope In → Scope, Scope Out → Limits; Evidence → Reads; Files → Scope; Behavior → Scenarios; Verify → Done means; Dependencies → Depends on: and Risks; Skills → per work group.
Resource: assets/plan-template.md.