add

Open, attach, or refresh optional GitHub PR delivery metadata/evidence for one OpenSpec story. Does not change story Status.

Archive a locally completed OpenSpec change workspace after pre-flight checks (review approved, tasks done, PR merged or explicitly waived). Thin wrapper over /opsx:archive.

Absorb structured review/tool, PR, or reviewer feedback into an OpenSpec initiative by routing it to story edits, review rework, story candidates, or initiative-level decisions. Use when feedback needs to be incorporated without bloating or drifting stories.

Interview-driven OpenSpec initiative planning — creates openspec/initiatives/<slug>/initiative.md with goal, context, story candidates, decisions, constraints, and external resources. Use when starting a new body of work that needs an OpenSpec-backed initiative before any change workspaces can be drafted.

Inspect the current or selected OpenSpec initiative, change, or spec state and recommend the single next workflow action with concise reasoning. Use when you need lightweight lifecycle routing before choosing a planning, implementation, PR, feedback, or archive command.

Claim one ready, unclaimed story from an OpenSpec initiative and execute it end-to-end, leaving a clean handoff. Use when starting a fresh session on a new story in an OpenSpec change workspace.

Run fresh claim/resume implementation passes against one OpenSpec change until it reaches Status: 🟣 IN REVIEW, becomes blocked, or the loop reaches a hard stop. Use when a plan-approved implementation story needs continuation only; independent review is intentionally left to a separate fresh session.

Run fresh plan-review and plan-resume sessions against one OpenSpec change until its Plan lane is approved, blocked, or the loop reaches a hard stop. Use when a story needs repeated independent plan feedback and feedback absorption before implementation or rework continues.

Pick up an OpenSpec change's planning contract — incorporate plan review feedback, complete unfinished spec sections, repair malformed story-plan scaffold anchors, or all three. Leaves implementation status unchanged except narrow TODO scaffold normalization and the Plan lane ready for review.

Review an OpenSpec change workspace's planning contract at any lifecycle point — validate Purpose / Actors / Scenarios / Acceptance / Verification / Critical Files / Locked Decisions against original intent, the live repo, and traceability gaps, then record a Plan Review verdict in the Plan lane.

Interview-driven creation of a new OpenSpec change workspace — writes proposal.md, story.md, design.md, tasks.md, and delta specs into openspec/changes/<story-slug>/ after interactive planning with proof-contract validation. Use when starting a new story under an existing OpenSpec initiative.

Resume implementation of an in-progress OpenSpec change story — picks up where the last session left off, applies red-first discipline, verifies implementation proof, and tracks progress through change workspace artifacts. Use when a fresh session needs to continue ongoing implementation work on an OpenSpec change.

Review one implemented OpenSpec change workspace from a fresh, oblivious session against its OpenSpec artifacts and live repo evidence. Read-only for code; writes only review coordination artifacts in the change workspace and optionally supplemental notebook findings.

Absorb structured review/tool, PR, or reviewer feedback into an epic by routing it to story edits, review rework, story candidates, or epic notes. Use when feedback needs to be incorporated without bloating or drifting stories.

Interview-driven bootstrap for a new epic — produces the agent_coordination/epics/<slug>/MASTER.md skeleton (header, goal/context, legend, empty story tracker) after a grillme-style walkthrough with the operator. Use when starting a new body of work that needs a coordination file before any stories can be drafted.

Open or refresh a GitHub PR for an entire epic, using CONTRACT.md and current DONE stories to produce an epic-level reviewer body. Use when completed epic scope should be sent to GitHub review as one coherent PR.

Squash non-archived DONE stories of an epic into its merged CONTRACT.md, verifying every claim against the codebase, detecting/fixing discrepancies, and archiving the stories. Use when an epic accumulates completed stories that should be folded into the authoritative contract.

Claim one ready story from an epic and execute it end-to-end, leaving a clean handoff. Use when starting a fresh session on a new story from an epic's MASTER.md tracker.

Run fresh claim, resume, and review sessions against one story until implementation is locally approved, blocked, or the loop reaches a hard stop. Use when an implementation story needs repeated independent review and continuation passes to converge.

Run fresh plan-review and plan-resume sessions against one story until its Plan lane is approved, blocked, or the loop reaches a hard stop. Use when a story needs repeated independent plan feedback and feedback absorption before implementation or rework continues.

Pick up a story's planning contract — incorporate plan review feedback, complete unfinished spec sections, or both. Leaves implementation status unchanged and the Plan lane ready for review.

Review a story's planning contract at any lifecycle point — validate Purpose / Actors / Scenarios / Acceptance / Verification / Critical Files / Locked Decisions against original intent, the live repo, and traceability gaps, then record a Plan Review verdict in the Plan lane.

Interview-driven creation of a new story for an existing epic — writes story-NN-<slug>.md and appends the MASTER.md tracker row with a draft planning lane after proof-contract validation.

Move one story from local review or local DONE into a GitHub PR, recording PR metadata on the story file. Optional stage between IN REVIEW and DONE.

Pick up one already in-progress story from an epic and continue it. Use when a fresh session needs to resume ongoing work on a specific story.

Review one implemented story against its spec, current repo state, and recorded handoff context. Read-only for code; updates only the story's coordination file.

Analyze whether one git ref merges cleanly into another and, when conflicts exist, trace them to PR, Jira, or ticket-backed intent before recommending a resolution. Use when a merge conflict needs evidence-backed analysis without changing code.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Reflect on the current session's friction points and propose patches to AGENTS.md, stories, or docs that would make future sessions smoother. Use at the end of a session to capture hard-won context before it is lost.