Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From openarche
Creates a structured execution plan with objective, acceptance criteria, capability-based steps, and coverage summary. Supports inspect, draft, revise, save.
npx claudepluginhub done-0/openarche --plugin openarcheHow this command is triggered — by the user, by Claude, or both
Slash command
/openarche:planThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Use this command to inspect, draft, revise, or save a real execution plan. Required behavior: 1. Build a plan with these fields: - `objective` - `acceptance criteria` - `execution steps` 2. Every execution step must include: - `title` - `capability` - `outcome` 3. Only use valid capability names: - `planning` - `worktree` - `browser` - `observability` - `review` - `maintenance` - `knowledge` 4. Keep the plan valid under current product rules: - objective must not be empty - there must be at least one acceptance criterion - there must be at l...
/plannewCreates new development plan from scratch using feature/project description. Enters plan mode, enforces TDD/DRY/SOLID principles, sets up tasks with strict rules.
/create-planCreates an implementation plan from arguments using the planning skill. Requires an active session started with /session-start or /session-continue.
/planCaptures user intent via 5 structured questions, creates strategic execution plan, saves to .claude/session-plan.md and session-intent.md for review.
/plan-newPlans complex projects with discovery, end state, success/kill criteria, assumptions, small phases, and verification. Writes Markdown plan file and shows summary.
/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.
Use this command to inspect, draft, revise, or save a real execution plan.
Required behavior:
objectiveacceptance criteriaexecution stepstitlecapabilityoutcomeplanningworktreebrowserobservabilityreviewmaintenanceknowledgeWhen presenting the plan, organize it into:
If the user asks to save it inside the live harness session, update .openarche/sessions/<plan-id>/state.json and keep the runbook.plan section valid.
If the user explicitly asks for a standalone document outside the live session, write it to the location they requested.