Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claudio
Creates actionable phase/task structures from planning input like files or descriptions, generating .claudio/phase*/ directories with tasks.md files and claude.md contexts for execution.
npx claudepluginhub vinnie357/claude-skills --plugin claudioHow this command is triggered — by the user, by Claude, or both
Slash command
/claudio:plan <plan_type> <input_source> [options]commands/claudio/The summary Claude sees in its command listing — used to decide when to auto-load this command
Create actionable implementation structures with organized phases and executable tasks from any planning input. Always generates `.claudio/phase*/` directories with ready-to-execute task contexts. **Flexible Input Patterns:** **Plan Types:** - `feature`: Single feature implementation structure - `project`: Complete project implementation structure - `migration`: System/data migration structure - `refactor`: Code refactoring and improvement structure - `integration`: System integration implementation structure - `enhancement`: Improvement and optimization structure **Input Sources:** - *...
/create_planCreates detailed implementation plans interactively by researching tickets, task descriptions, and codebase using specialized analysis agents.
/create_planCreates detailed implementation plans interactively by analyzing tickets, reading codebase files fully, gathering historical context, and spawning research agents.
/implementation-from-deep-researchCreates detailed implementation plans from tickets or files via deep codebase research, full file reads, and interactive analysis.
/planCreates detailed implementation plans interactively through research docs, file reads, and user dialog for features, refactors, or integrations.
/planCreates a step-by-step implementation plan from requirements or a PRD markdown file, then waits for user confirmation before any code changes.
/planBreaks project into small verifiable tasks with acceptance criteria, dependencies, checkpoints. Reads spec/codebase, presents plan for review, saves to tasks/plan.md and tasks/todo.md.
Share bugs, ideas, or general feedback.
Create actionable implementation structures with organized phases and executable tasks from any planning input. Always generates .claudio/phase*/ directories with ready-to-execute task contexts.
Flexible Input Patterns:
/claudio:plan feature "myprd.md" # Use external PRD file
/claudio:plan feature "add auth system with JWT" # Direct feature description
/claudio:plan enhancement "improve performance, use research on caching and optimization" # Description with research references
/claudio:plan myexisting_plan.md # Update existing plan structure
/claudio:plan refactor "modernize API layer" # Refactoring plan
Plan Types:
feature: Single feature implementation structureproject: Complete project implementation structuremigration: System/data migration structurerefactor: Code refactoring and improvement structureintegration: System integration implementation structureenhancement: Improvement and optimization structureInput Sources:
.claudio/research/ documents when mentioned.claudio/phase*/ structuresOutput Structure:
.claudio/phase1/, phase2/, etc. with organized development phasestasks.md files with specific, actionable development tasksclaude.md contexts for complex tasks with detailed guidanceResearch Integration: When you reference research (e.g., "use research on caching"), the plan automatically:
.claudio/research/ documentsTask with subagent_type: "plan-agent" - pass the project_path argument to transform any planning input into organized, actionable phase/task structures ready for immediate development execution.