sdcorejs-review-plan

Require user approval before executing write-code from sdcorejs-plan output.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-review-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdcorejs-review-plan
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-review-plan
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-review-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents expensive or incorrect code generation by enforcing an explicit user-approval step after a step-by-step plan is produced, but before any write-code orchestrator runs.

Core Features & Use Cases

  • Approval gate between planning and coding: Re-read the plan, run a strict self-review checklist, and require explicit user approval before dispatching the track write-code.
  • Cross-track plan verification: Applies to angular-portal, nestjs, and nextjs with the same gate logic while delegating only the actual code-writing step to the selected track orchestrator.
  • Snapshot persistence on approval: On approval, persist an approved plan snapshot via orchestration/auto-plans before triggering the write-code phase, ensuring auditability.

Quick Start

After sdcorejs-plan produces a plan, say “OK” (or “duyệt/approve”) to validate the plan is approved and allow the corresponding write-code orchestrator to run.

Frequently Asked Questions about sdcorejs-review-plan

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

FAQPage Schema
How do I enforce an approval gate between planning and code generation?

An approval gate blocks code generation by running a pre-approval self-review checklist on the plan and requiring explicit user affirmation before dispatching the write-code orchestrator.

Why do I need to review a plan before generating code task-for-task?

Reviewing a plan before generating code prevents expensive or incorrect code generation by enforcing an explicit user-approval step, ensuring the output strictly follows an approved contract.

Can I use this plan review gate across Angular, NestJS, and Next.js workflows?

Yes, cross-track plan verification applies the same approval gate logic to Angular, NestJS, and Next.js, delegating only the actual code-writing step to the selected track orchestrator.

How do I approve a plan to trigger the write-code orchestrator?

After the plan is produced, say “OK” or “approve” to validate the plan, which then allows the corresponding write-code orchestrator to run and generate code.

How does the plan approval gate maintain an audit trail for SDLC workflows?

Upon user approval, the gate persists an approved plan snapshot via orchestration auto-plans before triggering the write-code phase, ensuring full auditability for SDLC workflows.

Does the approval gate block code generation automatically if the plan fails review?

Yes, the gate blocks code generation until explicit approval is granted, running a deterministic self-review checklist first to ensure the plan meets strict safety requirements.