sdcorejs-plan

Convert approved software specs into ordered file-by-file plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents wasted engineering cycles by converting an approved spec into an explicit, numbered plan the user can verify before any code generation.

Core Features & Use Cases

  • Approved-spec to execution-ready plan: Turns the approved spec into a contract mapping files to ordered CREATE/EDIT tasks.
  • Track-aware phase grouping: Aligns plan structure and verification with the target track’s SDLC conventions and commands.
  • Path conflict detection: Glob-checks target project paths to surface CREATE/EDIT collisions before the user approves.
  • User confirmation gate: Hands off to sdcorejs-review-plan, which snapshots the plan and dispatches <track>-write-code only after approval.

Quick Start

Ask the AI to draft a plan first by saying: “Lên kế hoạch file-by-file trước khi code cho yêu cầu hiện tại.”

Frequently Asked Questions about sdcorejs-plan

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

FAQPage Schema
How do I create a file-by-file coding plan from an approved spec?

To create a file-by-file coding plan, trigger the planning phase by asking the AI to draft a plan from your approved spec. It converts the spec into an ordered, numbered list of CREATE/EDIT tasks mapped to specific files for review.

Why do I need to review an execution plan before code generation?

Reviewing an execution plan before code generation prevents wasted engineering cycles by surfacing path conflicts early. It establishes a contract-grade workflow, ensuring files and tasks align with track conventions before any code is written.

How do I check for file path conflicts before writing code in an SDLC workflow?

Checking for file path conflicts happens automatically during the planning phase. The system glob-checks target project paths to detect CREATE/EDIT collisions, surfacing them in the plan for you to verify before execution.

Does the SDCoreJS planning workflow support Next.js and Angular tracks?

Yes, the planning workflow supports Next.js and Angular portal tracks. It aligns the plan structure and verification commands with the specific SDLC conventions of these target tracks, with NestJS support planned.

What happens after I approve a file-by-file coding plan?

After you approve a file-by-file coding plan, the system hands off to the review component, which snapshots the plan and dispatches the track-specific write-code command to begin code generation.