Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/aidlc:planThe summary Claude sees in its command listing — used to decide when to auto-load this command
Execute the Workflow Planning stage, following `.aidlc/aidlc-rules/aws-aidlc-rules/core-workflow.md`. Load prior context from `aidlc-docs/`, decide which stages to run and at what depth, and present the plan (with validated Mermaid) for my approval. Do not proceed without confirmation.
Execute the Workflow Planning stage, following .aidlc/aidlc-rules/aws-aidlc-rules/core-workflow.md. Load prior
context from aidlc-docs/, decide which stages to run and at what depth, and
present the plan (with validated Mermaid) for my approval. Do not proceed
without confirmation.
npx claudepluginhub dynamicdevs/claudecode-aidlc-plugin --plugin aidlc/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.