Skip to content

[Phase 1] Bake the fixed critic rubric into Bob's planning prompt #599

Description

@github-actions

Story

As a maintainer relying on Bob's plans,
I want the BMAD Scrum Master prompt to carry the fixed quality rubric as an explicit self-check before it emits plan.json,
so that even before a separate critic step exists, Bob screens its own plan against the rubric, capturing much of the critic's value at near-zero cost.

Acceptance Criteria

  1. prompts/bmad/scrum-master.md gains a named quality-rubric section listing the fixed checks from discussion 💡 Adversarial Plan-Critic + Structural Gates for the Initiative-Planner (Bob) #593: no contested open-question baked into an acceptance criterion; an initiative-level success metric is present; a cost cap is present; untracked prerequisites are surfaced; each story is independently reviewable; and for eval/optimization stories, overfitting/reward-hacking and artifact-immutability are addressed.
  2. Each rubric item is phrased as a yes/no self-check, and the rubric instructs Bob to run it as a FINAL pass and route any unresolved item to open_questions rather than guessing (consistent with the existing no-invented-AC hard rule).
  3. The rubric lives in exactly one place (scrum-master.md, which the workflow prompt already instructs Bob to cat); the workflow inline prompt gains only a one-line pointer to run the rubric self-check, with no divergent second copy of the checklist.
  4. No schema or script behavior changes; the existing test suite still passes.

Tasks / Subtasks

Dev Notes

  • prompts/bmad/scrum-master.md is the single source Bob reads — the workflow inline prompt at .github/workflows/initiative-planner.yml:117-119 already tells Bob to cat it. Put the rubric there; do NOT fork a divergent copy into the workflow YAML.
  • The six findings the hand review of Initiative: Eval-gated, human-reviewed self-improving skills (SkillOpt-style) #581 surfaced (per discussion 💡 Adversarial Plan-Critic + Structural Gates for the Initiative-Planner (Bob) #593) ARE the rubric: contested-AC baked into ACs, no initiative success metric, no cost cap, reward-hacking/overfitting, untracked prereqs, and story reviewability.
  • scrum-master.md already has a hard rule (No invented acceptance criteria / unresolved -> open_questions) — extend it, do not contradict it.
  • This story defines the CANONICAL rubric text that the Phase-2 critic story (id 6) reuses verbatim — keep it self-contained and quotable so a second step can load it.

Project Structure Notes

Prompt-only change. Keep the rubric in scrum-master.md as the single source; the workflow already sources it, avoiding the drift that two copies would cause.

References

  • prompts/bmad/scrum-master.md
  • .github/workflows/initiative-planner.yml#L103-L176
  • tests/test_initiative_planner.bats

Likely target surface

  • prompts/bmad/scrum-master.md
  • .github/workflows/initiative-planner.yml

Story prepared by the BMAD Scrum Master (Bob) for epic #597. Status: ready-for-dev.

Metadata

Metadata

Assignees

No one assigned

    Labels

    dev-leadFor dev-lead agent pickupinitiativeEpic / initiative tracking issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions