claude

plan-readiness-review

Use right before publishing or handing off a large plan, and for every revision — one knock-down pass on the sections added after the draft, then a mechanical checklist that blocks publishing while any finding is unowned, any decision was answered by the planner instead of its owner, anything is used before it is defined, or the body mixes decisions with execution logs. Produces READINESS.md with the final YES/NO. Skip for chat-only sketches that will not be executed.

1 on GitHubupdated 1 month ago
/

Plugin plan-readiness-review from marketplace devfellowship in devfellowship/skills. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (1)

  • plan-readiness-review

    Use right before publishing or handing off a large plan, and for every revision — one knock-down pass on the sections added after the draft, then a mechanical checklist that blocks publishing while any finding is unowned, any decision was answered by the planner instead of its owner, anything is use

View source on GitHub

More from devfellowship/skills

All 11 plugins →

Analyze collected Campaigns post metrics for one social account. Use for weekly performance reports, retrospective rankings, or evidence-based content experiments. Do not use to publish content, schedule reports, or claim causation.

1 skill

1

Use BEFORE writing a plan for large software work — a new app, a redesign, a mobile version, a cross-service pipeline or integration, anything that will become 3+ PRs or be executed by other agents. Routes through the pack in a fixed order (ground truth → two-planner draft → acceptance gates → PR slicing → readiness review → execution handoff), names the file each phase produces and the hard gates a plan must pass before it is published. Skip for a one-file bug fix, a question, or a small edit to a plan that already exists.

1 skill

1

Use sempre que for abrir uma task de trabalho pela ferramenta `create_task` do MCP — inclusive quando a task nasce de um plano, de uma conversa ou de uma PR. Garante que a task nasça com etapa, com o "por quê" e ligada ao plano certo. Não use para editar task existente.

1 skill

1

Use when writing the acceptance criteria, rollout and risk sections of a large plan, and as the checklist a reviewer attacks a finished draft with. Turns every prose promise into a gate that can fail on its own — checks on the running build, a viewport × input × content matrix, a default-path and flag-exit rule, shared-state isolation, the human who must see each output, measured limits, test hygiene and real-device proof. Pipelines, webhooks and integrations use non-ui-gates.md. Skip only for a pure refactor with no user-visible output, no flag, no limit and no shared state.

1 skill

1

Use to draft a large plan with two independent planner agents — shared brief, blind drafts from different angles and models, an optional cross-read, a merge that picks instead of averaging, an adversarial review that tries to knock the plan down, a written dialog where the author may argue back, and a consistency pass with a draft verdict. Use after plan-ground-truth. Skip for editing an existing plan; for a small plan use the single-planner prompt in prompts.md.

1 skill

1

Use when a large plan is about to be executed by agents or people, and when resuming execution after a crash or handoff — executor briefs by section reference, who merges, verification tools by path, resource budget, requester corrections mid-flight, and the definition of done (seen running on the path real users get). Skip for executing a one-PR plan yourself.

1 skill

1

Maintain plan-readiness-review?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins11 plugins