Stats
Actions
Tags
From CAST — Claude Agent Specialist Team
Creates an implementation plan using the planner agent, reading project config and writing a task breakdown with dependency order to a dated markdown file.
How this command is triggered — by the user, by Claude, or both
Slash command
/cast:planThe summary Claude sees in its command listing — used to decide when to auto-load this command
Use the `planner` agent to create an implementation plan for the following request: $ARGUMENTS Read the project's CLAUDE.md and package.json first to understand the stack. Write the plan to `~/.claude/plans/YYYY-MM-DD-<feature-name>.md`. Return a task breakdown with dependency order.
Use the planner agent to create an implementation plan for the following request:
$ARGUMENTS
Read the project's CLAUDE.md and package.json first to understand the stack. Write the plan to ~/.claude/plans/YYYY-MM-DD-<feature-name>.md. Return a task breakdown with dependency order.
npx claudepluginhub ek33450505/claude-agent-team --plugin cast/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.
/planStarts Manus-style file-based planning: creates task_plan.md, findings.md, progress.md if missing, invokes planning skill, and guides through workflow.
/planInteractively builds Goal, Scope, Metric, and Verify command for an autoresearch run from provided goal description.
/planRestates requirements, assesses risks, creates step-by-step implementation plan with phases, dependencies, complexity estimates, and waits for user confirmation.
/planCaptures user intent, analyzes requirements, and generates a weighted execution plan saved to .claude/session-plan.md. Does not execute — plans are saved for review or later execution via /octo:embrace.