unikit-plan

Solid

Create an implementation plan for a feature — a dependency-ordered, actionable task list for the project. Has three modes: fast (a quick single-pass plan), full (a richer plan that can also create a git branch), and add (extend an existing plan with more tasks). Pick the mode from the user's wording: "full plan" runs full; "quick plan" or "fast plan" runs fast; a plain "create a plan" with no qualifier defaults to fast; "add to the plan" or "extend the plan" runs add. Use whenever the user wants to plan a feature or task, e.g. "create a plan", "create a full plan", "create a quick plan", "plan this feature", "just plan this", "add this to the plan", "extend the plan", "add a phase to the plan".

AI & Automation 16 stars 1 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# {{engine_name}} Feature Plan Generator Create a structured feature plan and roadmap for the current {{engine_name}} project. Three modes: - **Fast** — quick plan, no git branch, saves to `.unikit/code/PLAN.md` - **Full** — optionally creates `<git.branch_prefix><name>` git branch (when `git.enabled` and `git.create_branches`), asks preferences, saves to `.unikit/code/plans/<dated-folder>/` - **Add** — modify/extend an existing plan without creating a branch **Output artifacts by mode:** **Fast mode** → single flat file `.unikit/code/PLAN.md`: - Contains everything: overview, settings, checklist, commit plan, dependency graph, and a `## Technical Context` section with plan-brief content (always generated based on current codebase state). - Temporary plan for quick work — `/unikit-implement` may offer deletion after completion. **Full mode** → folder `.unikit/code/plans/{YYYY-MM-DD}_{feature-name}/`: - **`TASKS.md`** — actionable checklist with WHY context per task, effort estimates, file paths, commit plan, dependency graph. - **`PLAN-BRIEF.md`** — always created. Structured technical brief (constraints, interfaces, key patterns, dependency graph, files) for the implementing agent, based on current codebase state at planning time. When a research is linked (from `/unikit-explore`), the plan references it via `## Based on` using the Research Reference Format below. The research's `RESEARCH_BRIEF.md` is used as **input** for generating the plan's own `PLAN-BRIEF.md`, not...

Details

Author
NintendaDev
Repository
NintendaDev/unikit-ai
Created
3 months ago
Last Updated
5 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

make_plan

Creates a detailed, multi-document implementation plan for a software feature or task before any code is written. Use when the user wants to "make a plan", types "make_plan", or asks to "plan this feature", "create an implementation plan", "plan out this work", or "write a spec/plan" for something to be built. Drives a mandatory clarifying-questions interview, a hard Zero-Ambiguity Gate, and produces a `plans/<feature>/` document set ending in a task-by-task execution plan. For EXECUTING an existing plan, use the exec_plan skill instead.

4 Updated 2 days ago
blendsdk
Web & Frontend Listed

feature-plan

Take a feature the user has in mind and turn it into a co-authored, code-level feature implementation plan (featurePlan-<slug>.html) — file-by-file change manifest in build order, pseudo-code, edge cases, and open questions the human decides, all grounded in this repo's actual code. The user resolves questions and edits sections in the browser; exported human edits are tagged and override the AI draft. Use when the user asks for a feature implementation plan, a code-level breakdown, or says "featurePlan".

1 Updated yesterday
MohanTn
AI & Automation Solid

unikit-implement

Execute the tasks from an already-created feature plan in .unikit/code/plans/ — read the plan (TASKS.md + PLAN-BRIEF.md), work through the uncompleted tasks in order, write the code, mark progress, and resume across sessions. Supports selective runs by phase or by task numbers, and continuing from where the last session stopped. Use whenever a plan exists and the user wants to build it, e.g. "implement", "implement the plan", "start coding", "execute the plan", "run the plan", "do the next task", "implement phase 3", "implement tasks 2.1 and 2.3", "continue implementation", "continue where we left off", "keep going on the feature". To create the plan first, use the planning skill — this one carries an existing plan out.

16 Updated 5 days ago
NintendaDev