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/BRIEF.md
View on GitHubGenerated from PLAN.md @ <hash> — do not edit
# <Project name> — plan brief
<!-- Generation rules (drop these comments from the generated file):
- Line 1 is the stamp, exactly as above. <hash> is the first 12 hex characters
of `git hash-object .plan/PLAN.md`, taken from the PLAN.md the brief was
generated from. A brief whose stamp differs from PLAN.md's current hash is
stale and is regenerated before anyone reads it.
- This file is written to `.plan/BRIEF.md` and tracked on the plan branch.
Where the Artifact tool exists, the same content is also published as an
artifact; the file is the brief, the artifact only renders it.
- Every section is generated from PLAN.md and names its source section in the
italic line under its heading. Never add content PLAN.md does not hold: if
the brief needs something, it goes into PLAN.md first.
- Hand edits are overwritten at the next regeneration, by design. Whoever
edits PLAN.md regenerates this file in the same commit.
- One page: aim for under ~100 lines. Plain language — no protocol detail. -->
> One page to check this plan against what you expect. Feedback goes in chat
> (or as comments on the artifact): it is applied to `PLAN.md`, and this brief
> is regenerated from it.
## Outcome
*From `PLAN.md` › Requirements › Outcome.*
<The outcome in the user's own words, two or three sentences.>
## Day to day
*From `PLAN.md` › Requirements › Day to day.*
```mermaid
flowchart LR
%% Where the user is, which device, what they do, what happens while they
%% are away. One node per step, in plain words.
A[<user starts X on device>] --> B[<what runs>]
B --> C[<what they see or approve>]
```
## Constraints and out of scope
*From `PLAN.md` › Requirements › Constraints and Out of scope.*
**Constraints, ranked:**
1. <Constraint — the one that wins a conflict.>
2. <Constraint.>
**Out of scope:** <item>; <item>.
## Decisions
*From `PLAN.md` › Frozen decisions and Plan review.*
| ID | Decision | Group | Status |
|---|---|---|---|
| D-1 | <the decision, one line> | Needs you | <answered / pending — blocks S2> |
| D-2 | <the decision, one line> | Decided | <reason in a clause> |
| D-3 | <the decision, one line> | Default for now | <revisit when …> |
<!-- One row per frozen decision, in PLAN.md's order. Fixed protocol entries
(Git strategy, Worktree strategy, Final review stage) are left out. -->
**Plan review lenses:** <Lens> — <trigger that fired>; <Lens> — <trigger>.
<Or, before the review has run: "not run yet".>
## Done when
*From `PLAN.md` › Requirements › Done.*
- [ ] <A check a script or a person can run.>
- [ ] <Check.>
## Stage map
*From `PLAN.md` › Stage index & dependencies.*
```mermaid
flowchart LR
S0[S0 <name>] --> S1[S1 <name>]
S0 --> S2[S2 <name>]
S1 --> SF[SF Plan review]
S2 --> SF
```
<!-- One node per stage, one edge per `depends` entry. Mark a `gate: human`,
`gate: local` or `gate: live` stage in its label, e.g. `S3[S3 <name> · human]`
or `S4[S4 <name> · live]`. -->
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 |