Plan review tests

Skill ChristopherAlphonse/calphonse-skills/plan-review-tests

Curated skills and configurations for AI-assisted development

Install

npx -y skills add ChristopherAlphonse/calphonse-skills --skill plan-review-tests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Produces a test diagram, identifies coverage gaps, and writes a .planning QA handoff artifact.

SKILL.md

2.1 KB, as published. Nobody here has run it

Plan Review Tests

Verify that the plan has enough test coverage.

Guardrails

Start from success criteria and failure modes, then choose tests.
Prefer the smallest test set that gives confidence for the changed behavior.
Follow existing test framework and file placement before proposing new tooling.
Do not require broad coverage unrelated to the plan.

Test Diagram

Create an ASCII diagram covering:

New user-visible flows.
New data flows.
New codepaths.
New branches, outcomes, and failure states.
External integrations and mocked boundaries.

For each node, list the expected test type: unit, integration, end-to-end, contract, regression, visual, accessibility, load, or eval.

Coverage Review

Check:

Happy paths.
Nil, empty, invalid, and upstream-error paths.
User interaction edge cases: double submit, slow network, navigation away, stale state, back/forward.
Rollout and rollback behavior.
Observability assertions where meaningful.
Existing test conventions before recommending new framework or layout.

For LLM or prompt changes, inspect local project guidance such as AGENTS.md, CLAUDE.md, or .planning/* for eval patterns. If no eval guidance exists, recommend a small reference dataset and deterministic regression checks.

Artifact

Write a QA handoff to:

.planning/qa/test-plan-{branch}-{YYYYMMDD-HHMMSS}.md

Use this structure:

# Test Plan
Generated by /plan-eng-review on {date}
Branch: {branch}
Plan: {plan-path}

## Affected Pages/Routes
- {path} - {what to test and why}

## Key Interactions
- {interaction}

## Edge Cases
- {edge case}

## Critical Paths
- {flow}

## Non-UI Checks
- {command, endpoint, or behavior}

Output

Return the test diagram, missing tests, eval needs, and QA handoff path.

Install: npx skills add ChristopherAlphonse/calphonse-skills --skill plan-review-tests