Conducting Plan Review

Evaluate implementation plans against a 35-item quality checklist.

17|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/cipherstash/cipherpowers --skill conducting-plan-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Conducting Plan Review
Source: https://github.com/cipherstash/cipherpowers/tree/main/plugin/skills/verifying-plans
Command: npx skills add https://github.com/cipherstash/cipherpowers --skill conducting-plan-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates costly implementation failures by systematically evaluating plans against comprehensive quality standards before execution begins.

Core Features & Use Cases

  • Comprehensive Quality Checklist: Reviews 35 items across 6 categories including security, testing, architecture, and error handling.
  • Structured Feedback Generation: Creates detailed evaluation reports with blocking issues and improvement suggestions.
  • Use Case: When your team creates an implementation plan for a new authentication system, use this Skill to identify missing security considerations, inadequate test coverage, and architectural flaws before development starts.

Quick Start

Review the implementation plan located at .work/2024-01-15-user-auth.md using the plan review workflow.

Frequently Asked Questions about Conducting Plan Review

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

FAQPage Schema
How do I review an implementation plan before starting development?

Plan review systematically evaluates implementation plans against quality standards across six categories—security, testing, architecture, error handling, code quality, and process—identifying blocking issues and improvement suggestions before execution begins, preventing costly failures.

What should a quality checklist for code review include?

A comprehensive quality checklist covers 35 items across security and correctness, testing coverage, architectural soundness, error handling, code quality standards, and process adherence, ensuring thorough evaluation before implementation starts.

When should I conduct a plan review during software development?

Conduct plan review after drafting implementation plans and before execution begins, especially for high-stakes work like authentication systems, to catch missing security considerations, inadequate testing, and architectural flaws early.

How do I identify security gaps in an implementation plan?

Plan review evaluates security and correctness against established standards, flagging missing security considerations, vulnerable patterns, and authentication gaps as blocking issues or suggestions before development proceeds.

What's the difference between blocking issues and suggestions in plan evaluation?

Blocking issues represent critical failures that must be resolved before execution; suggestions indicate improvements recommended for code quality, testing, or process. Plan review categorizes findings to prioritize action.

Can plan review assess task completeness and granularity?

Yes, plan review evaluates whether implementation tasks are sufficiently granular, complete, and detailed across all quality dimensions, ensuring plans are executable and comprehensive before development begins.