From hope
Orchestrates the hope pipeline end-to-end — session setup, intent, shape, consult, bond — with configurable engagement levels (autonomous, collaborative, guided).
How this command is triggered — by the user, by Claude, or both
Slash command
/hope:fullThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /hope:full ORCHESTRATE. Run the hope pipeline end-to-end. **Task:** $0 ## Session Setup Ask: "How would you like to work? Autonomous / Collaborative [default] / Guided?" Detect session type from the task: Build, Debug, Plan, or Reflect. Emit: `[SESSION] Pipeline: [phases] | Engagement: [level]` ## Pipeline 1. **Intent** — Clarify WHAT. If the task arrives with structured input (proposal, specs, task list), validate rather than re-clarify. Complete when you have a clear objective and acceptance criteria. 2. **Shape** — Decide HOW. Get expert perspectives on the approach. Skip for ...
ORCHESTRATE. Run the hope pipeline end-to-end.
Task: $0
Ask: "How would you like to work? Autonomous / Collaborative [default] / Guided?"
Detect session type from the task: Build, Debug, Plan, or Reflect. Emit:
[SESSION] Pipeline: [phases] | Engagement: [level]
Intent — Clarify WHAT. If the task arrives with structured input (proposal, specs, task list), validate rather than re-clarify. Complete when you have a clear objective and acceptance criteria.
Shape — Decide HOW. Get expert perspectives on the approach. Skip for Reflect sessions or trivially clear tasks. Complete when you have a concrete approach and first step.
Consult (optional) — Shape already includes consultation. This is an additional review pass if the user wants a second opinion. For Reflect sessions, consult is the primary stage.
Bond (when needed) — If the task spans multiple modules and warrants parallel agents, design and create a team.
Execute — For solo paths, proceed with the shaped approach.
The pipeline is a map, not a rail. Skip stages that don't apply. Come back to earlier stages if the task reveals new information.
npx claudepluginhub saadshahd/moo.md --plugin hope/planCreates strategic execution plans by capturing user intent, analyzing requirements, and generating a weighted execution strategy saved to .claude/session-plan.md.
/create-planCreates an implementation plan from arguments using the planning skill. Requires an active session started with /session-start or /session-continue.
/plan-modeInitiates a multi-agent planning consultation to create a structured implementation plan with task hierarchy and specialist dispatches, producing a plan document without code changes.
/generateGenerates a structured plan using Hypo-Workflow methodology, following consultation-first action boundary and four-rule discipline. Produces a mini-contract for execution authorization.
/create-planCreates detailed implementation plans through interactive research and iteration, with configurable autonomy levels (autopilot, critical, verbose) to control how much user input is requested during planning.
/workflowInteractive guide to a 5-command project lifecycle workflow. Asks user context and directs to the appropriate command for exploration, planning, session management, or feature addition.