dev-plan
/dev-plan
Strategic planning with optional interview workflow. Use when the user wants to plan before implementing — "plan this", "let's plan", structured requirements gathering for vague ideas. Pairs with @compass-planner agent. Supports consensus mode and review mode.
- Author
- evolution-foundation ↗
- Repository
- evo-nexus ↗
- Licence
- Apache-2.0
- Last repository change
- 12.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.05.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Strategic planning with optional interview workflow. Use when the user wants to plan before implementing — "plan this", "let's plan", structured requirements gathering for vague ideas. Pairs with @compass-planner agent. Supports consensus mode and review mode.
Triggers from the description
Original author description
Strategic planning with optional interview workflow. Use when the user wants to plan before implementing — "plan this", "let's plan", structured requirements gathering for vague ideas. Pairs with @compass-planner agent. Supports consensus mode and review mode.
How it works
- Use When
- Do Not Use When
- Why This Exists
- Execution Policy
- Mode Selection
- Quality Gates
- Handoff
- Delegation
SKILL.md preview
---
name: dev-plan
description: Strategic planning with optional interview workflow. Use when the user wants to plan before implementing — "plan this", "let's plan", structured requirements gathering for vague ideas. Pairs with @compass-planner agent. Supports consensus mode and review mode.
---
# Dev Plan
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Plan creates comprehensive, actionable work plans through intelligent interaction. It auto-detects whether to interview the user (broad requests) or plan directly (detailed requests).
## Use When
- User wants to plan before implementing — "plan this", "plan the", "let's plan"
- User wants structured requirements gathering for a vague idea
- User wants an existing plan reviewed — "review this plan"
- User wants multi-perspective consensus on a plan — see `dev-ralplan` (Tier 1, imported in EPIC 3)
- Task is broad or vague and needs scoping before any code is written
## Do Not Use When
- User wants autonomous end-to-end execution → use `dev-autopilot` instead
- User wants to start coding immediately with a clear task → delegate to `@bolt-executor`
- User asks a simple question that can be answered directly → just answer it
- Task is a single focused fix with obvious scope → skip planning, just do it
## Why This Exists
Jumping into code without understanding requirements leads to rework, scope creep, and missed edge cases. Plan provides structured requirements gathering, expert analysis, and quality-gated plans so that execution starts from a solid foundation.
## Execution Policy
- Auto-detect interview vs direct mode based on request specificity
- Ask one question at a time during interviews — never batch multiple questions
- Gather codebase facts via `@scout-explorer` agent before asking the user about them
- Plans must meet quality standards: 80%+ claims cite file/line, 90%+ criteria are testable
- Save plans to `workspace/projects/plans/{name}.md`
## Mode Selection
| Mode | Trigger | Behavior |
|------|---------|----------|
| Interview | Default for broad requests | Interactive requirements gathering |
| Direct | `--direct`, or detailed request | Skip interview, generate plan directly |
| Review | `--review` | Critic evaluation of an existing plan |
## Quality Gates
- All claims about the codebase must cite file:line
- All acceptance criteria must be testable
- Open questions must be explicitly listed
- Trade-offs must be documented for non-trivial decisions
## Handoff
After plan is approved by user:
- Pass plan path to `@bolt-executor` for implementation
- Or chain to `dev-autopilot` for full lifecycle execution
## Delegation
For deeper structured planning, hand off to `@compass-planner` agent — it runs a tighter interview workflow with mandatory user confirmation gates.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · evolution-foundation/evo-nexus | 90 | Apache-2.0 |
| raccoon-office/box-agent | 100 | MIT |
| classmethod/tsumiki | 100 | MIT |
| yz200202/dev-plan-skill | 95 | MIT |
| HarunRRayhan/RayStack | 90 | MIT |
| TrinhVanHiep/bdt-kit | 90 | MIT |
Database snapshot: 13.11.2026 · package version 8134f8b0350f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90plan
Strategic planning with optional interview workflow. Activate when user says: plan this, plan the, let's plan, make a plan, how should we approach. - 100plan-feature
Structured feature planning workflow. Use when the user says "plan a feature", "design this", "how should we build", "feasibility check", or any pre-implementation planning work. Covers requirements, investigation, feasibility, and implementation planning. - 100plan
Use when a task needs structured planning before implementation. Supports --delegate and round=N[,M,...]. - 90dev-ralplan
Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic. - 100plan
[Planning] Use when a workflow step or the user asks for implementation planning. --mode=review supports review-only or --fix-loop; validate interviews, execute implements. --mode=ci plans CI fixes; --mode=cro plans conversion optimization. - 100plan
[Planning] Use when a workflow step or the user asks for implementation planning. --mode=review supports review-only or --fix-loop; validate interviews, execute implements. --mode=ci plans CI fixes; --mode=cro plans conversion optimization.