sdcorejs-review-spec

Review AI-generated SDLC spec files and require user approval before planning.

2|Updated Apr 18, 2026

Search Tags:#agent orchestration #spec review #approval workflow #bilingual #sdcl #auto snapshot

Ready to run

npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-review-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdcorejs-review-spec
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-review-spec
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-review-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents ambiguous or incomplete specs from moving into planning by enforcing an explicit user approval step after sdcorejs-write-spec generates the spec file.

Core Features & Use Cases

Approval gate for SDLC flow: Re-reads the generated spec, runs a self-review checklist, and blocks progression until the user explicitly approves.
Bilingual, track-agnostic review: Applies consistently across angular-portal, nestjs, and nextjs while keeping template-driven file paths aligned.
Snapshot persistence on approval: On explicit approval, persists an approved spec snapshot via orchestration/auto-specs and only then hands off to sdcorejs-plan.

Quick Start

Trigger by asking to review the spec, then confirm with OK once the concise summary looks correct.

Frequently Asked Questions about sdcorejs-review-spec

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

FAQPage Schema

How do I enforce a manual approval gate for AI-generated spec files before planning begins?▼

Spec review blocks planning progression until you explicitly approve the generated spec, running a mandatory self-review checklist and presenting a concise summary for confirmation before proceeding.

How to review and approve SDLC spec files across different frameworks like NestJS and Next.js?▼

Bilingual spec review applies consistently across angular-portal, nestjs, and nextjs, keeping template-driven file paths aligned while presenting a concise spec summary for your approval.

What happens after I approve a spec during the review workflow?▼

After spec approval, the system persists an approved spec snapshot via orchestration/auto-specs and then hands off control to the planning phase to continue the workflow.

Does the spec approval workflow support bilingual review for Angular portals?▼

Yes, the bilingual spec review workflow supports angular-portal, nestjs, and nextjs, applying consistent review logic and maintaining template-driven file path alignment across all frameworks.

Why does planning not start automatically after the spec file is generated?▼

Planning is blocked because the approval gate requires a mandatory self-review checklist and explicit user confirmation to prevent ambiguous or incomplete specs from moving into planning.