Coordinate planning and tracking of large-scale features across multiple subsystems.
npx skills add https://github.com/SYUNTA99/NS-ENGINE --skill plan-large-scale
Please help me install this Agent Skill. Skill: plan-large-scale Source: https://github.com/SYUNTA99/NS-ENGINE/tree/main/.claude/skills/plan-large-scale Command: npx skills add https://github.com/SYUNTA99/NS-ENGINE --skill plan-large-scale
Coordinate planning and tracking of large-scale features across multiple subsystems to ensure structured delivery.
Follow the two-layer workflow to initialize current as the investigation workspace and create planning files under .claude/plans/<feature>.
High-intent search queries and answers about installing and using this skill.
To coordinate large-scale features, use a two-layer workflow with a persistent planning layer (.claude/plans) for investigations and subplans, plus an execution layer (.claude/plans/current) to manage staged implementation and track progress across subsystems.
Breaking down big features involves creating structured subplans and investigation milestones. By maintaining traceable findings and decisions in a dedicated planning workspace, you can decompose complex initiatives into manageable, staged implementation tasks.
A structured feature delivery workflow is needed when projects involve new files, module changes, or API alterations requiring coordinated plans. It manages investigation findings and staged implementation to ensure structured delivery across multiple subsystems.
Initialize the planning workspace by creating the execution layer as the investigation workspace (.claude/plans/current) and generating planning files under .claude/plans/<feature>. This separates persistent plans from active execution tracking.
Yes, the two-layer workflow separates persistent planning from active execution. The persistent planning layer (.claude/plans) stores investigation findings and decisions, while the execution layer (.claude/plans/current) manages active subplan progress.
The two-layer planning workflow is designed for large-scale features requiring new files, module changes, or API alterations. It may be excessive for simple, single-file modifications or minor updates that do not require coordinated plans or investigation milestones across subsystems.
davidabeyerExtract user-selected proposals into a structured brief for the /plan command.
akaiHuangReview React/TypeScript/JavaScript files for code quality and performance issues.
tikazyqMonitor execution plan progress and track SubPlan and Round statuses.
ImperialAutomationBreak down complex GitHub issues into sub-issues and a tracking draft PR.
