Slice-plan refinement
Refine an existing executable plan in place. Do not create another plan,
implement product code, or change the selected story outcome.
Require a refinable plan
Require an existing executable plan and this project's context required by
dough-slice-planning, especially any supplied
target, hard limit, exceptions, overrun policy, and the plan lifecycle.
- If no plan exists, use
dough-slice-planning.
- If a plan is marked as awaiting story refinement after resplitting, use
dough-story-refinement on its mapped
story and realign the plan before treating it as refinable or executable.
- If the selected story's goal, scope, or examples must change, use
dough-story-refinement.
- If the parent problem, candidate selection, or sibling ordering must change,
use dough-story-decomposition.
- After the assessment below, if the cumulative design is supported and all
remaining slices are cohesive and single-proof-loop, meet any supplied target,
and have no unexplained path beyond a supplied hard limit,
report
ready for direct execution; no further refinement is required.
Execution still requires separate authorization from the invoking workflow.
Refine the plan
Read the plan and only the code and tests needed to judge execution boundaries.
Read and apply:
Preserve completed slices, applicable evidence, and the selected story's goal
and scope.
Assess the cumulative design, including how remaining examples build on
completed slices, then classify each remaining slice:
| Result |
Decision |
| Ready |
One Behavior/Structure gate, one proof loop, a cohesive path consistent with the cumulative model, and a plausible hypothesis under any supplied target |
| Refine |
Same story, but the slice has multiple beats, unsupported special-case design, low confidence, or a supplied target or hard-limit concern |
| Escalate |
Learning requires selected-story or parent-story review |
A suspected accidental contractual restriction uses the shared
plan-conflict handoff
before a conflicting plan edit; classify it as Escalate, not an automatically
correctable special case. Route other Escalate findings through the input gate.
Refine every remaining Refine slice.
After an overrun, confirm attempt-owned work is safely parked or reverted before
editing the plan. Stop for human judgment when ownership is unclear. Do not
commit, push, implement, or verify product behavior unless the invoking workflow
separately authorizes it.
Count the resulting plan's slices, including completed slices but excluding
obsolete replaced slices. If the count is greater than 15, report
story resplit recommended: <count> slices; use dough-resplit-story and link to
dough-resplit-story. This is a recommendation,
not an automatic invocation or a new execution-readiness gate. Do not resplit
the story or change its backlog placement during slice-plan refinement.
Report the plan path, replaced slices, resulting slice count, sizing exceptions,
any resplit recommendation, and whether execution can resume. End with:
## SLICE PLAN REFINED
1---2name: dough-slice-plan-refinement-33description: Refines an existing executable plan in place into smaller, proof-owned Behavior/Structure slices. Use after dough-slice-planning when slices are complex, cumulative design accumulates special cases, sizing confidence is low, or execution overruns. Creates no new plan and does not change the selected story outcome.4---56# Slice-plan refinement78Refine an existing executable plan in place. Do not create another plan,9implement product code, or change the selected story outcome.1011## Require a refinable plan1213Require an existing executable plan and this project's context required by14[dough-slice-planning](../dough-slice-planning/SKILL.md), especially any supplied15target, hard limit, exceptions, overrun policy, and the plan lifecycle.1617- If no plan exists, use `dough-slice-planning`.18- If a plan is marked as awaiting story refinement after resplitting, use19 [dough-story-refinement](../dough-story-refinement/SKILL.md) on its mapped20 story and realign the plan before treating it as refinable or executable.21- If the selected story's goal, scope, or examples must change, use22 [dough-story-refinement](../dough-story-refinement/SKILL.md).23- If the parent problem, candidate selection, or sibling ordering must change,24 use [dough-story-decomposition](../dough-story-decomposition/SKILL.md).25- After the assessment below, if the cumulative design is supported and all26 remaining slices are cohesive and single-proof-loop, meet any supplied target,27 and have no unexplained path beyond a supplied hard limit,28 report `ready for direct execution`; no further refinement is required.29 Execution still requires separate authorization from the invoking workflow.3031## Refine the plan3233Read the plan and only the code and tests needed to judge execution boundaries.34Read and apply:3536- [slice decomposition](../dough-story-decomposition/references/problem-decomposition.md#decompose-slices),37 including its cumulative design assessment, sizing, and escalation rules; and38- [active-plan refinement](../dough-story-refinement/references/planning.md#refine-the-active-plan),39 including executable proof ownership.4041Preserve completed slices, applicable evidence, and the selected story's goal42and scope.4344Assess the cumulative design, including how remaining examples build on45completed slices, then classify each remaining slice:4647| Result | Decision |48| --- | --- |49| **Ready** | One Behavior/Structure gate, one proof loop, a cohesive path consistent with the cumulative model, and a plausible hypothesis under any supplied target |50| **Refine** | Same story, but the slice has multiple beats, unsupported special-case design, low confidence, or a supplied target or hard-limit concern |51| **Escalate** | Learning requires selected-story or parent-story review |5253A suspected accidental contractual restriction uses the shared54[plan-conflict handoff](../dough-execute-plan/references/execution-decisions.md#resolve-a-disputed-plan-restriction)55before a conflicting plan edit; classify it as Escalate, not an automatically56correctable special case. Route other Escalate findings through the input gate.57Refine every remaining Refine slice.5859After an overrun, confirm attempt-owned work is safely parked or reverted before60editing the plan. Stop for human judgment when ownership is unclear. Do not61commit, push, implement, or verify product behavior unless the invoking workflow62separately authorizes it.6364Count the resulting plan's slices, including completed slices but excluding65obsolete replaced slices. If the count is greater than 15, report66`story resplit recommended: <count> slices; use dough-resplit-story` and link to67[dough-resplit-story](../dough-resplit-story/SKILL.md). This is a recommendation,68not an automatic invocation or a new execution-readiness gate. Do not resplit69the story or change its backlog placement during slice-plan refinement.7071Report the plan path, replaced slices, resulting slice count, sizing exceptions,72any resplit recommendation, and whether execution can resume. End with:7374`## SLICE PLAN REFINED`