software-plan-review

Reviews software delivery plans and produces structured critiques with prioritized recommendations.

902|58|Updated May 31, 2012
One-click install
npx skills add https://github.com/stencila/stencila --skill software-plan-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-plan-review
Source: https://github.com/stencila/stencila/tree/main/.stencila/skills/software-plan-review
Command: npx skills add https://github.com/stencila/stencila --skill software-plan-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivery plans often contain vague tasks, broken sequencing, missing testing strategies, or gaps against their source design. This Skill critically reviews an existing software delivery plan and produces a structured critique so teams can fix weaknesses before implementation begins.

Core Features & Use Cases

  • Structured Plan Critique: Evaluates plans against an expected structure covering summary, design reference, prerequisites, phases, testing strategy, risks, and definition of done.
  • Design Alignment Checking: Loads the referenced design from .stencila/designs/ and verifies the plan covers all acceptance criteria without adding or dropping scope.
  • TDD Slice Assessment: Judges whether TDD slices are too broad, too narrow, or well-sized, and suggests merging or splitting slices.
  • Use Case: After generating a phased implementation plan for a user-auth feature, ask for a review to catch sequencing problems (e.g., token validation must precede middleware integration), missing exit criteria, and unaddressed design risks before work starts.

Quick Start

Review the delivery plan stored at .stencila/plans/user-auth-flow.md and give me a prioritized critique.

Frequently Asked Questions about software-plan-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a software implementation plan before starting work?

Provide the plan text or reference a stored plan under .stencila/plans/. The review checks structure, task granularity, phase sequencing, testing strategy, risks, and definition of done, then returns findings with severity ratings and prioritized recommendations.

What makes a good software delivery plan review checklist?

A strong checklist covers summary and design traceability, prerequisites, concrete task breakdown, phase ordering with working increments, per-phase testing, documentation tasks, risk mitigations, and a verifiable definition of done aligned with design acceptance criteria.

Can a plan be reviewed without a source design document?

Yes. The plan is reviewed on its own merits for structure, sequencing, and actionability, but the absence of a source design is noted as a limitation because coverage and alignment cannot be fully verified.

How do I know if my TDD slices are the right size?

Well-sized slices each cover one meaningful behavior with a clear red-green-refactor cycle. Slices batching many unrelated tests are too broad; runs of trivial adjacent slices touching the same code should be merged into behavior-oriented units.

When should I not use a plan review skill?

Do not use it for writing production code, creating a design from scratch, reviewing source code, or drafting a new plan. It is intended for critiquing an existing plan artifact, not initial creation.