Repository navigation
Open
Labels
dev-lead:hands-offOpt an item out of the dev-lead persona automation entirelyOpt an item out of the dev-lead persona automation entirelyinitiativeinitiative:hold
Description
Story
As a Decider,
I want every test result in brief.md §6 and one summary comment against the Graduation criteria and "say no" conditions,
so that the approve / close / re-park decision is on record with reasons that will still make sense in a year.
Acceptance Criteria
- Each of
brief.md§6 rows 1–5 has a dated Result entry: a value, "not shown", or "not run" with a reason. - A summary comment lists the five results against Graduation criteria (a) and (b) in
brief.md§7 and the "say no" conditions, and reports criterion (c) as "not testable in this programme". - The comment follows the story 1 brand checklist.
- The decision is recorded with a date: approval only if every Graduation criterion is met or explicitly revised in
brief.md§7 with a dated reason; otherwise a comment saying why not (decision pending, closed or re-parked). - Elapsed working days from the first test to the decision comment are recorded (SM-6).
Tasks / Subtasks
- Confirm every §6 row has a dated Result (AC: chore: seed org secrets baseline in .gitignore #1)
- Write and post the summary comment (AC: chore: bootstrap from repo-template #2, [Fleet Monitor] combsmith/worldchest — .github/workflows/add-to-project.yml #3, docs: seed planning artifacts from the incubator package (graduation) #5)
- Record the decision (AC: [Fleet Monitor] combsmith/worldchest — .github/workflows/sonarcloud.yml #4)
Dev Notes
- Source: PRD FR-8, UJ-4, SM-6; brief §7 Graduation criteria and "say no" conditions.
- Criterion (c) — an end-to-end restore by a non-technical user — needs product code and cannot pass in this programme. Per PRD FR-8 [NOTE FOR PM], approval is not recorded while (c) is unrun unless the Decider first revises §7 with a dated reason or separately authorises a restore prototype.
- The decision is the human Decider's; this story only assembles the record.
- Which Discussion carries the summary and decision (incubator docs: seed planning artifacts from the incubator package (graduation) #5 per the PRD, or worldchest WorldChest — evidence programme (graduated from incubator #5) #6) is an open question.
Project Structure Notes
Edits _bmad-output/planning-artifacts/brief.md §6 Result column; may also require a dated revision of §7 if the Decider revises criteria.
References
- https://github.com/combsmith/worldchest/blob/main/_bmad-output/planning-artifacts/prd.md (FR-8, UJ-4, §8 SM-6)
- https://github.com/combsmith/worldchest/blob/main/_bmad-output/planning-artifacts/brief.md (§6, §7)
Story prepared by the BMAD Scrum Master (Bob) for epic #7. Status: ready-for-dev.
Metadata
Metadata
Assignees
Labels
dev-lead:hands-offOpt an item out of the dev-lead persona automation entirelyOpt an item out of the dev-lead persona automation entirelyinitiativeinitiative:hold
Activity
don-petry commentedon Oct 21, 2026
dev-lead is withholding action on this item.
It is labeled
dev-lead:hands-off(deliberately kept off-limits to dev-lead (e.g. changes to the dev-lead automation itself)), so dev-lead will not pick it up while that label is present. This notice is posted once so the withhold is visible rather than looking like a stalled run.To re-enable automated pickup: remove the
dev-lead:hands-offlabel.