Skill definition
hi-plan
Plan implementations, design architectures, create technical roadmaps with detailed phases.
SKILL.md
Plan - Implementation Planning
Scan ./plans/ first. If relevant unfinished plans exist, update them. If unclear, ask user.
Cross-Plan Dependency Detection
- Scan
plans/*/plan.md(status != completed/cancelled) - Detect overlapping files, shared deps, same feature area
- Classify: new needs existing output ->
blockedBy: [dir], new changes existing deps -> update both - Bidirectional: update BOTH plan.md files
Default (No Arguments)
| Operation | Description |
|---|---|
| (default) | Create implementation plan (fast mode) |
--full | Full flow: research + scope challenge + red team + validate |
archive | Archive plans + log |
red-team | Adversarial review |
validate | Critical questions interview |
If invoked without arguments, run fast mode trực tiếp (không AskUserQuestion).
Workflow Modes
| Flag | Mode | Research | Red Team | Validation |
|---|---|---|---|---|
| default / --fast | Fast | Skip | Skip | Skip |
| --full | Full | 1 researcher | Optional | Optional |
| --hard | Hard | 2 researchers | Yes | Optional |
| --parallel | Parallel | 2 researchers | Yes | Optional |
| --two | Two approaches | 2+ researchers | After select | After select |
Add --no-tasks to skip task hydration.
Process Flow (default fast)
- Cross-Plan Scan -> Chỉ quét nếu có plan active (scan nhanh)
- Scope Challenge -> Skip (fast)
- Codebase Analysis -> Đọc docs, scan nếu cần (không spawn researcher)
- Plan Documentation -> Write plan.md + phase-XX.md
- Hydrate Tasks -> TaskCreate per phase (--no-tasks để skip)
- Output -> Absolute path
Full Flow (--full)
- Pre-Creation Check -> Check Plan Context
- Cross-Plan Scan -> Detect blockedBy/blocks, update both
- Scope Challenge -> Run 3 questions, select mode
- Research -> Spawn 1 researcher
- Codebase Analysis -> Read docs, scan if needed
- Plan Documentation -> Write plan.md + phase-XX.md
- Red Team ->
/hi-plan red-team {path} - Validate ->
/hi-plan validate {path} - Hydrate Tasks -> TaskCreate per phase
- Output -> Absolute path + craft command
Output Requirements
- Plans in CURRENT WORKING PROJECT DIRECTORY (not user home)
- Plan files = persistent. Tasks = session-scoped
- Invoke /hi-project-organization after output
- Respect
./docs/development-rules.md
Task Management
- Auto-hydrate tasks after plan write (skip --no-tasks)
- <3 phases -> skip task creation (overhead > benefit)
- Task tools CLI-only (VSCode: use TodoWrite)
Subcommands
| Subcommand | Purpose |
|---|---|
/hi-plan archive | Archive plans + log |
/hi-plan red-team {path} | Adversarial review |
/hi-plan validate {path} | Critical questions interview |
Continue exploring
Related skills
hi-predictFive expert personas independently analyze proposed changes before implementation to catch architectural, security, performance, and UX issues early. Uses mind_mcp for project context and graph_mcp for code impact analysis. Produces GO/CAUTION/STOP verdict with consensus agreements, conflict resolutions, and risk mitigations. Use before major features, refactors, or risky changes.hi-reverseReverse Engineering C and C++ modules into validated use-case, module, and C++-to-Java migration artifact packages. Generates evidence-backed traces, sequence/class/state/activity/architecture diagrams, entry-point/interface/data/business-rule/error/concurrency catalogs, parity mappings, risks, tests, reviews, and coverage; exhaust mind_mcp and graph_mcp before Serena, and use native source tools only as a final fallback.hi-sequential-thinkingApply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.