Skills create-plan
Create a structured implementation plan with phases and complexity scores
install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/brunoscardoso/plan-flow/create-plan" ~/.claude/skills/openclaw-skills-create-plan && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/brunoscardoso/plan-flow/create-plan" ~/.openclaw/skills/openclaw-skills-create-plan && rm -rf "$T"
manifest:
skills/brunoscardoso/plan-flow/create-plan/SKILL.mdsource content
Create Plan
Create a structured implementation plan based on a discovery document or user input.
What It Does
- Extracts requirements from discovery document (or user input)
- Analyzes scope and complexity
- Structures phases with complexity scores (0-10)
- Assigns tasks to each phase
- Ensures tests are always the last phase
Usage
/create-plan <discovery_document> /create-plan "<feature_description>"
Arguments:
: Path to discovery document (recommended)discovery_document
: Direct description of feature (if no discovery)feature_description
Output
Creates:
flow/plans/plan_<feature>_v<version>.md
Complexity Scoring
| Score | Level | Description |
|---|---|---|
| 0-2 | Trivial | Simple, mechanical changes |
| 3-4 | Low | Straightforward implementation |
| 5-6 | Medium | Moderate complexity, some decisions |
| 7-8 | High | Complex, multiple considerations |
| 9-10 | Very High | Significant complexity/risk |
Plan Structure
# Plan: [Feature Name] ## Overview Brief description ## Goals - Goal 1 - Goal 2 ## Phases ### Phase 1: [Name] **Scope**: What this phase covers **Complexity**: X/10 - [ ] Task 1 - [ ] Task 2 **Build Verification**: Run `npm run build` ### Phase N: Tests (Final) **Scope**: Write comprehensive tests **Complexity**: X/10 - [ ] Unit tests - [ ] Integration tests ## Key Changes 1. **Category**: Description
Example
/create-plan @flow/discovery/discovery_user_auth_v1.md
Critical Rules
- No Code: Plans describe what to implement, not how to code it.
- Tests Last: Tests are always the final phase.
- No Auto-Chaining: Do NOT auto-invoke
./execute-plan
Next Command
After creating a plan, review it and then run
/execute-plan @flow/plans/plan_<feature>_v1.md.