project-planner

Converts design documents into step-by-step implementation plans with file paths, code snippets, and verification criteria.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Coral5644/NekansModPack --skill project-planner-coral5644
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-planner
Source: https://github.com/Coral5644/NekansModPack/tree/main/.cursor/skills/project-planner
Command: npx skills add https://github.com/Coral5644/NekansModPack --skill project-planner-coral5644

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level design document into actionable development work is error-prone: tasks end up too vague, dependencies are unclear, and AI agents lack the context to execute changes. This Skill transforms brainstorming output into a fine-grained implementation plan where every task specifies exact file paths, complete code snippets, and in-game verification criteria. ## Core Features & Use Cases - Task Decomposition: Breaks a design into 5-30 minute tasks ordered by dependency, layered bottom-up from data layer to logic, communication, UI, and integration. - Structured Task Cards: Each task includes estimated duration, dependencies, parallelization flags, exact file paths, paste-ready code, verification standards, and a commit message. - Dependency Graphs & Checkpoints: Generates a text-based dependency diagram and marks manual in-game testing checkpoints with test steps and expected behavior. - Use Case: After finishing a brainstorming session for a new game feature, run this Skill to produce an execution plan saved to Docs/plans/, ready for the executing-plans skill to implement in batches. ## Quick Start Use the project-planner skill to turn my design document into a step-by-step implementation plan with task cards and verification checkpoints.

Frequently Asked Questions about project-planner

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

FAQPage Schema
How do I break a software design into executable tasks?▼

Scan the existing codebase first, then decompose the design bottom-up across data, logic, communication, UI, and integration layers. Each task should take 5-30 minutes, produce one committable change, and include exact file paths, complete code snippets, and verification criteria.

What should an AI-executable implementation plan include?▼

Each task card needs estimated duration, dependencies, parallelization flags, exact file paths to create or modify, paste-ready code snippets, verification standards, and a commit message. The plan also needs a dependency graph and manual testing checkpoints.

How do I verify code changes without unit tests?▼

Define verification standards as in-game observable behavior or code-level checkable results. Insert manual checkpoints after core logic, UI binding, and integration milestones, each specifying test steps and expected phenomena.

When should I not use a detailed implementation plan?▼

Skip detailed planning when the design document and requirement boundaries are not yet confirmed; run brainstorming first. Also avoid planning features outside the requirement scope, following DRY and YAGNI principles.

How do I handle tasks involving unfamiliar APIs in a plan?▼

Verify unfamiliar APIs through documentation research before writing the task card, or explicitly mark the task as needing a spike. High-risk tasks involving unverified engine behavior must include a fallback or degradation strategy.