by-carlos/plan-staged-rollout / skills/staged-rollout
staged-rollout
UnverifiedRun a large build as many small, resumable sessions by decomposing it into a `.plan/` folder of dependency-ordered stages with an evidence ledger, then executing one stage per fresh session. Use when the user says "this is too big for one session", "plan a staged rollout", or describes a multi-day build that needs cross-session progress tracking.
references/templates/LEDGER.md
View on GitHub# <Project name> — build ledger
Statuses: `todo → doing → done`, plus `blocked` (waiting on a human or an
external gate — the stage becomes a runbook) and `skipped` (decided against,
one-line reason). Partial completion is a normal, resumable state.
Keep table rows to **ONE line** — detail goes in the notes block below, never
in a table cell. Sessions read the status table plus only the notes blocks of
the stages they `depend` on (the final review stage reads all of it). Update
your stage's row and notes block at the end of every session (Operating
protocol, finish protocol).
## Status
| Stage | Status | Verified | Date | Result |
|---|---|---|---|---|
| S0 <stage name> | todo | — | — | — |
| S1 <stage name> | todo | — | — | — |
| ... | ... | ... | ... | ... |
| SF Plan review | todo | — | — | — |
## Notes
As-built notes, acceptance evidence, gotchas, handoff notes, follow-ups. One
block per stage; sessions read only the blocks of their `depends` stages.
### S0 <stage name>
_(empty)_
### S1 <stage name>
_(empty)_
<!-- One ### S<N> block per stage. Templates for the states you'll hit:
done — paste the real acceptance output, then the as-built summary and
any gotchas the next stage needs to know.
actuals — every session on the stage, whatever its outcome, adds one
`Actuals:` line (`scripts/effortlog.py usage`, its `line` as is);
`/plan-close` sums them against the estimates. A stage is
recorded `done` only once `scripts/estimates.py check` passes;
where `usage` cannot run, an `Actuals waived: <reason>` line
stands in for the `Actuals:` line.
artifacts — the finish protocol adds one `Artifacts check:` line
(`scripts/artifacts_check.py`, its line as is); a record, never
a gate — the final review judges each `outside` line.
doing — tick the completed Steps checkboxes in the stage file; write a
handoff note here (what's left, where to resume).
blocked — record exactly what human/external action unblocks it, as a
runbook the human can follow; no faked progress. Where that row
and runbook get committed depends on whether the stage branch
exists yet — see PLAN.md, Operating protocol, "Recording a
block". A mid-stage block lands on the stage branch, so this
file's copy on the plan branch keeps reading `doing` and the
block is recorded in BLOCKED.md instead. Discovered mid-run that
the stage needs a resource only the local machine has? Use the
literal reason `needs-local` in the Result cell (or the
BLOCKED.md section) instead of a generic note — see PLAN.md,
"Recording a block", "The discovered case".
skipped — one-line reason; if this stage owned acceptance/verification
work nothing else covers, say so here too, so SF sees it.
follow-up — a shortcut or scope-creep item spotted here that became (or
should become) its own stage; name it so the review stage sees it.
added — a stage added after the scaffold opens its notes block with its
`Added by` line and the scope referee's verdict (PLAN.md,
"Adding a stage").
-->
### SF Plan review
_(empty)_
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |