skills.rest
son-nguyen-301
son-nguyen-301COMMUNITY
Explore all skills by this author →
GitHub

review-plan

Apply five review lenses to a plan and generate structured findings.

Updated Apr 6, 2026
Search Tags:#security#qa#software#plan-review#review-analysis#lenses
One-click install
npx skills add https://github.com/son-nguyen-301/hydra-claude --skill review-plan-son-nguyen-301
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/son-nguyen-301/hydra-claude/tree/main/skills/review-plan
Command: npx skills add https://github.com/son-nguyen-301/hydra-claude --skill review-plan-son-nguyen-301

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This tool provides a structured methodology to review plans by applying five established lenses (Staff Engineer, Tech Lead, SRE, Security, QA), generating concrete findings, and writing a standardized review file for governance and traceability.

Core Features & Use Cases

  • Applies five review lenses to a provided plan and returns a comprehensive findings set.
  • Writes a review file at the expected location following the prescribed template, enabling reproducible governance.
  • Integrates with the plan-loading workflow to ensure the review always reflects the current plan content and context.

Quick Start

Run the review-plan skill against a loaded plan to generate a plan review file.

Frequently Asked Questions about review-plan

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

FAQPage Schema
What is a structured plan review and how does it improve software engineering governance?▼

A structured plan review applies five established lenses—Staff Engineer, Tech Lead, SRE, Security, and QA—to analyze technical proposals and generate concrete findings. This produces a standardized review file for governance and traceability.

How do I systematically review a software development plan for security and QA gaps?▼

To review a plan for security and QA gaps, apply the five review lenses—Staff Engineer, Tech Lead, SRE, Security, and QA—to the loaded plan content. This generates structured findings written to a standardized review file.

What perspectives should I include when doing a technical plan review?▼

A technical plan review should include Staff Engineer, Tech Lead, SRE, Security, and QA perspectives. Applying these five lenses ensures analysis covers architecture, execution, reliability, vulnerability, and testing dimensions.

Does this plan review approach work without loading external plan content?▼

No, this review approach requires loading plan content via the read-plan skill first. The analysis operates on a provided plan path and needs the loaded content to generate accurate findings and write the review file.

What is the best way to document plan review findings for team traceability?▼

The best way to document plan review findings is writing a standardized review file at the expected location using a prescribed template. This ensures reproducible governance by generating concrete, structured outputs from the five review lenses.

Related Skills

Explore More Software Engineering Skills→
shishishishi
3

scrum-team-product-owner

Automate backlog management by creating PBIs aligned to a Product Goal.

Community
Basic
nnexainnexai
1

gsd-code-review

Analyze source code changes for bugs, security vulnerabilities, and quality issues.

Community
Advanced
AMDResearchAMDResearch
3

pm-review

Creates/manages structured code, design, or document review workflows with severity-based findings and traceability.

Official
Advanced
son-nguyen-301son-nguyen-301

review-code

Apply seven code-review lenses to changed files and write structured findings.

Community
Advanced