Stats
Actions
Tags
From one-for-all
Break work into small verifiable tasks with acceptance criteria and dependency ordering
How this command is triggered — by the user, by Claude, or both
Slash command
/one-for-all:ofa-plancommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
Invoke the one-for-all:planning-and-task-breakdown skill. Token discipline: default to concise `standard` output. Use `lite` only when the scope is small, low-risk, obvious to verify, and needs no deeper analysis. Escalate to `strict` when risk, ambiguity, failing verification, or the user explicitly asks for deeper analysis. Read the existing spec from `specs/` (or an equivalent project-approved spec path) and the relevant codebase sections. Then: 1. Enter plan mode — read only, no code changes 2. Identify the dependency graph between components 3. Slice work vertically (one complete pa...
Invoke the one-for-all:planning-and-task-breakdown skill.
Token discipline: default to concise standard output. Use lite only when the scope is small, low-risk, obvious to verify, and needs no deeper analysis. Escalate to strict when risk, ambiguity, failing verification, or the user explicitly asks for deeper analysis.
Read the existing spec from specs/ (or an equivalent project-approved spec path) and the relevant codebase sections. Then:
Keep the response concise: summarize the phase order, key risks, and verification. Save the plan to tasks/plan.md and task list to tasks/todo.md.
npx claudepluginhub danieldev24/one-for-all --plugin one-for-all