Delivery planning
Purpose
Turn an accepted .play model into a delivery plan: how many slices of which type, in which
order, who can work in parallel, what each group costs, and when it is done. The model already
cuts the work into slices and names the events between them, so the plan counts and orders
those slices instead of guessing at features.
Planning does not replace modeling, review or the render and gap-fill gates. A plan is a
working note, not a contract: when the model changes, recount; when a slice is not accepted,
it is not planned work yet.
Ground rules
- Count slices, not features. The unit is one slice of one type
(
StateChange, StateView, Automation, Translate). Method and weights:
references/slice-counting.md.
- Estimates are ranges from the team's own history. State the basis (which completed slices,
how many, how long). With no history the estimate is a first estimate without history:
say so, give a wide range, and replace it as soon as slices complete. Never quote an accuracy
figure or a duration you cannot trace to a count and a rate.
- Events are the contract. Slice B depends on slice A because B needs an event or view A
produces. Anyone can build B against the events A will produce, with synthetic
given
events, before A is finished. Dependencies are read from the model, not remembered.
- Render is not free of effort, and gap-fill is not free of risk. Stage renders
StateChange and StateView; Automation and Translate are hand-written against the
model as contract. Check admission per slice with cratis-screenplay-render-and-gap-fill
(tool versions: cratis-screenplay-toolchain SKILL.md) before pricing a slice as
rendered.
- Plans live in
.ai-work/; tracking lives in GitHub issues where the repository works
that way. Never put a plan in the model, in .cratis/, or in a documentation folder.
Procedure
- Confirm the scope is accepted. Only slices of a committed model under the root count
as planned delivery. Drafts and open questions are listed separately as unplanned. If the
model is still moving, plan only the stable modules and say what is excluded.
- Inventory the slices. Use the Screenplay MCP:
describe-application for counts and
paged children, dependency-graph at slice level for edges, cycles and an advisory
order, dependencies and find-references per slice for the contracts it consumes and
produces and for the invokes, action and form edges the graph does not order (reads maps to decidesFrom, which it does order, but it stays a coordination point). Treat complete: false or an ambiguous binding as unknown, never as no
dependency (cratis-screenplay-model-authoring). Without the MCP, read the .play files.
- Classify each slice by type and by realization: rendered (Stage admits it) or
hand-written (gap-fill, adapter, external call). Record the reason for each hand-written one.
- Build the dependency table (
references/parallel-delivery.md): per slice, the events
it consumes, who produces each, and the slices it waits on. A cycle means a feedback loop:
return it to slice design (usually an Automation slice); never schedule around it.
- Group into waves. Slices with no unmet producers form wave 1; each next wave needs
only earlier waves. Within a wave, slices are independent and can run in parallel. Group
slices that share one view or one stream into one slice group (one issue).
- Weigh and estimate (
references/velocity-and-capacity.md): apply the team's weights per
type and realization, divide by measured throughput, and report a range with its basis. Add
separate lines for what is not slice work: modeling and review gates, integration with
outside systems, environment and deployment, specifications that need new infrastructure.
- Track. One GitHub issue per slice group, in the repository's own issue practice
(assign the issue, keep an in-progress status in the issue body, check for an existing claim
before starting): the status block lists the slices, their
type, the wave, the blockers and each slice's planning status below. The issue's own state
follows the repository's hygiene (in progress, in review when the PR opens, paused, blocked,
done only when delivered). Keep the working plan in
.ai-work/<task>/delivery-plan.md.
- Re-plan after each completed group. Update throughput, recount if the model changed,
restate the range. Record the retrospective metrics from
references/velocity-and-capacity.md.
Status vocabulary
Per-slice planning status, a closed set recorded inside the plan and the issue's status block.
It is not the issue's state: the enclosing issue keeps the repository's own states (for example
in progress, in review, paused, blocked, done), and is done only when its slices are
delivered (merged and released where the repository releases).
| Status |
Meaning |
| todo |
accepted in the model, not started |
| in progress |
one owner is working on it |
| blocked |
waiting on a named producer, decision or external party; say which |
| done |
built, its specifications pass, and the slice conforms to the model |
Before claiming a slice, check its current status. If it is already in progress, someone else
holds it: pick another slice, do not take it over and do not report an error. Move a status only
to a different value; a repeated update is a signal that another worker got there first.
Check for an existing claim (assignee and in-progress status) before starting; where the harness
provides a claim tool such as issue_work, its claim step is that guard.
What a plan states
- Scope: the modules and slices counted, and what was excluded and why.
- Slice counts by type, split into rendered and hand-written.
- The dependency table and the waves.
- The estimate as a range with its basis, or "first estimate without history".
- Capacity assumptions: who or what works in parallel, and the constraints on it.
- Risks that move the range: hand-written slices, outside systems, open questions, a model
likely to change.
Limits
- A rate from one project or one person does not transfer to another team or another kind of
slice; say when the sample is small or mixed.
- Counting hides unusually large slices. A slice that needed a design discussion is two slices
or a modeling question; recount rather than weigh it as "big".
- Parallel work only pays when slices are truly independent in the dependency table and
integration of the shared events is owned. Shared writes to one file, one stream or one
external system serialize the work.
References
references/slice-counting.md - types, realization, weights, what to count and exclude.
Read when counting or classifying slices.
references/velocity-and-capacity.md - measuring throughput, ranges, capacity math,
retrospective metrics. Read when producing or updating an estimate.
references/parallel-delivery.md - dependency table, waves, event contracts, issue
grouping. Read when splitting work across people or agents.
references/provenance.md - sources and what was not adopted.
Related skills
cratis-screenplay-slice-design (slice dependencies), cratis-screenplay-model-authoring
(MCP navigation), cratis-screenplay-render-and-gap-fill (what renders, gap-fill handoff),
cratis-screenplay-modeling-lifecycle (phases and gates).
1---2name: cratis-screenplay-delivery-planning3description: Use when estimating an accepted Screenplay scope, ordering slice dependencies or dividing and tracking delivery across people or agents. Not for deciding model behavior, reviewing the model or rendering individual slices.4license: MIT5metadata:6 source: https://skillmd.com/skills/cratis/cratis-screenplay-delivery-planning7---89# Delivery planning1011## Purpose12Turn an accepted `.play` model into a delivery plan: how many slices of which type, in which13order, who can work in parallel, what each group costs, and when it is done. The model already14cuts the work into slices and names the events between them, so the plan counts and orders15those slices instead of guessing at features.1617Planning does not replace modeling, review or the render and gap-fill gates. A plan is a18working note, not a contract: when the model changes, recount; when a slice is not accepted,19it is not planned work yet.2021## Ground rules22- **Count slices, not features.** The unit is one slice of one type23 (`StateChange`, `StateView`, `Automation`, `Translate`). Method and weights:24 `references/slice-counting.md`.25- **Estimates are ranges from the team's own history.** State the basis (which completed slices,26 how many, how long). With no history the estimate is a *first estimate without history*:27 say so, give a wide range, and replace it as soon as slices complete. Never quote an accuracy28 figure or a duration you cannot trace to a count and a rate.29- **Events are the contract.** Slice B depends on slice A because B needs an event or view A30 produces. Anyone can build B against the events A will produce, with synthetic `given`31 events, before A is finished. Dependencies are read from the model, not remembered.32- **Render is not free of effort, and gap-fill is not free of risk.** Stage renders33 `StateChange` and `StateView`; `Automation` and `Translate` are hand-written against the34 model as contract. Check admission per slice with `cratis-screenplay-render-and-gap-fill`35 (tool versions: `cratis-screenplay-toolchain` `SKILL.md`) before pricing a slice as36 rendered.37- **Plans live in `.ai-work/`; tracking lives in GitHub issues** where the repository works38 that way. Never put a plan in the model, in `.cratis/`, or in a documentation folder.3940## Procedure411. **Confirm the scope is accepted.** Only slices of a committed model under the root count42 as planned delivery. Drafts and open questions are listed separately as unplanned. If the43 model is still moving, plan only the stable modules and say what is excluded.442. **Inventory the slices.** Use the Screenplay MCP: `describe-application` for counts and45 paged children, `dependency-graph` at slice level for edges, cycles and an advisory46 order, `dependencies` and `find-references` per slice for the contracts it consumes and47 produces and for the `invokes`, action and form edges the graph does not order (`reads` maps to `decidesFrom`, which it does order, but it stays a coordination point). Treat `complete: false` or an ambiguous binding as unknown, never as no48 dependency (`cratis-screenplay-model-authoring`). Without the MCP, read the `.play` files.493. **Classify each slice** by type and by realization: rendered (Stage admits it) or50 hand-written (gap-fill, adapter, external call). Record the reason for each hand-written one.514. **Build the dependency table** (`references/parallel-delivery.md`): per slice, the events52 it consumes, who produces each, and the slices it waits on. A cycle means a feedback loop:53 return it to slice design (usually an Automation slice); never schedule around it.545. **Group into waves.** Slices with no unmet producers form wave 1; each next wave needs55 only earlier waves. Within a wave, slices are independent and can run in parallel. Group56 slices that share one view or one stream into one slice group (one issue).576. **Weigh and estimate** (`references/velocity-and-capacity.md`): apply the team's weights per58 type and realization, divide by measured throughput, and report a range with its basis. Add59 separate lines for what is not slice work: modeling and review gates, integration with60 outside systems, environment and deployment, specifications that need new infrastructure.617. **Track.** One GitHub issue per slice group, in the repository's own issue practice62 (assign the issue, keep an in-progress status in the issue body, check for an existing claim63 before starting): the status block lists the slices, their64 type, the wave, the blockers and each slice's planning status below. The issue's own state65 follows the repository's hygiene (in progress, in review when the PR opens, paused, blocked,66 done only when delivered). Keep the working plan in67 `.ai-work/<task>/delivery-plan.md`.688. **Re-plan after each completed group.** Update throughput, recount if the model changed,69 restate the range. Record the retrospective metrics from `references/velocity-and-capacity.md`.7071## Status vocabulary72Per-slice planning status, a closed set recorded inside the plan and the issue's status block.73It is not the issue's state: the enclosing issue keeps the repository's own states (for example74in progress, in review, paused, blocked, done), and is done only when its slices are75delivered (merged and released where the repository releases).7677| Status | Meaning |78|---|---|79| todo | accepted in the model, not started |80| in progress | one owner is working on it |81| blocked | waiting on a named producer, decision or external party; say which |82| done | built, its specifications pass, and the slice conforms to the model |8384Before claiming a slice, check its current status. If it is already `in progress`, someone else85holds it: pick another slice, do not take it over and do not report an error. Move a status only86to a different value; a repeated update is a signal that another worker got there first.87Check for an existing claim (assignee and in-progress status) before starting; where the harness88provides a claim tool such as `issue_work`, its claim step is that guard.8990## What a plan states91- Scope: the modules and slices counted, and what was excluded and why.92- Slice counts by type, split into rendered and hand-written.93- The dependency table and the waves.94- The estimate as a range with its basis, or "first estimate without history".95- Capacity assumptions: who or what works in parallel, and the constraints on it.96- Risks that move the range: hand-written slices, outside systems, open questions, a model97 likely to change.9899## Limits100- A rate from one project or one person does not transfer to another team or another kind of101 slice; say when the sample is small or mixed.102- Counting hides unusually large slices. A slice that needed a design discussion is two slices103 or a modeling question; recount rather than weigh it as "big".104- Parallel work only pays when slices are truly independent in the dependency table and105 integration of the shared events is owned. Shared writes to one file, one stream or one106 external system serialize the work.107108## References109- `references/slice-counting.md` - types, realization, weights, what to count and exclude.110 Read when counting or classifying slices.111- `references/velocity-and-capacity.md` - measuring throughput, ranges, capacity math,112 retrospective metrics. Read when producing or updating an estimate.113- `references/parallel-delivery.md` - dependency table, waves, event contracts, issue114 grouping. Read when splitting work across people or agents.115- `references/provenance.md` - sources and what was not adopted.116117## Related skills118`cratis-screenplay-slice-design` (slice dependencies), `cratis-screenplay-model-authoring`119(MCP navigation), `cratis-screenplay-render-and-gap-fill` (what renders, gap-fill handoff),120`cratis-screenplay-modeling-lifecycle` (phases and gates).