niko-plan
Niko Memory Bank System - Plan Phase - Implementation Planning
Best use case
niko-plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Niko Memory Bank System - Plan Phase - Implementation Planning
Teams using niko-plan should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/niko-plan/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How niko-plan Compares
| Feature / Agent | niko-plan | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Niko Memory Bank System - Plan Phase - Implementation Planning
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Plan Phase - Implementation Planning This command creates a detailed implementation plan for the current task. Planning depth scales with complexity level — this file routes to the appropriate level-specific planning document. ## Step 1: Load Memory Bank Files Read: - `memory-bank/tasks.md` - `memory-bank/activeContext.md` ## Step 2: Determine Complexity Level Read the complexity level from `memory-bank/activeContext.md` If no complexity level is set, or `memory-bank/activeContext.md` does not exist: STOP PLANNING! Invoke the `niko` skill to initialize the memory bank and perform complexity analysis, then proceed as instructed there. ## Step 3: Route to Level-Specific Planning Load the appropriate complexity level-specific Niko workflow file, then use its phase mappings to proceed to the Plan phase.
Related Skills
sw-tech-stack-planner
Use when user wants a tech stack recommendation, technology choices, docker-compose setup, or architecture decisions for a software project – reads vision.md, user-stories.md, use-cases.md and generates requirements/tech-stack.yaml silently.
self-explanatory-code-commenting
Guidelines for GitHub Copilot to write comments to achieve self-explanatory code with less comments. Examples are in JavaScript but it should work on any language that has comments. Triggers on: **
prd-planner
Analyzes PRDs and creates beads task breakdown for multi-agent implementation
plans-management
Manages Plans.md tasks and marker operations. Use when user mentions タスクを追加, Plans.md更新, 完了マーク, タスク状態変更, add task, update plans, mark complete. Do NOT load for: 実装作業, レビュー, Plans.md以外のファイル操作.
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
plan
Creates detailed implementation plan from validated research. Produces task breakdown with dependencies.
plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
plan-reduce-max-lines
This skill should be used when reducing the maximum class/module lines threshold and fixing all violations. It updates the RuboCop configuration, identifies classes and modules exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized files.
plan-maker
Create implementation plans with testable acceptance criteria, validation strategies, integration touchpoints, and risk analysis before coding begins.
implementation-planner
专业的软件架构师,根据用户需求和设计方案创建详细的实施(开发)计划。将设计方案转化为可执行的任务列表,支持测试驱动开发和渐进式实现。
dev-workflow-planning
Structured development workflows using /brainstorm, /write-plan, and /execute-plan patterns. Transform ad-hoc conversations into systematic project execution with hypothesis-driven planning, incremental implementation, and progress tracking.
default-planner
Analyze user requests and create executable task plans for any type of work. Use this skill when the work type is unclear, spans multiple domains (frontend+backend+infra), or doesn't fit specialized planners. Triggered by general requests like "build an app", "create a system", or "implement a solution".