mine-plan-exec

Executes a governed implementation plan end to end in a MINE-managed linked worktree.

16|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/6ixGODD/mine --skill mine-plan-exec-6ixgodd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mine-plan-exec
Source: https://github.com/6ixGODD/mine/tree/main/plugins/mine/skills/mine-plan-exec
Command: npx skills add https://github.com/6ixGODD/mine --skill mine-plan-exec-6ixgodd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-session software projects lose engineering state when plans live only in conversation context. This Skill executes a single MINE-registered implementation plan as an immutable contract, keeping dependency checks, code changes, verification, commits, and execution-graph updates consistent and traceable across sessions and agents. ## Core Features & Use Cases - Dependency-gated execution: Resolves the requested plan ID against the execution graph, verifies all hard predecessors are ACCEPTED, and refuses to run BLOCKED, REJECTED, or already-ACCEPTED nodes. - Isolated worktree implementation: Prepares and works only on the MINE-managed plan/<id>-<slug> branch via mine plan prepare, never on stable or dev, with dirty-workspace classification and explicit-path staging. - Evidence-bound reporting: Runs required verification gates, writes an acceptance report under docs/plan/reports/, and records implementation evidence through MCP tools or the JSON CLI fallback. - Use Case: A user invokes mine-plan-exec plan03 to implement a scoped design change; the Skill checks the graph, starts the plan, edits code in the linked worktree, runs tests and linters, commits, and marks the node IMPLEMENTED for independent review. ## Quick Start Ask the agent to execute plan plan03 with mine-plan-exec and let it prepare the worktree, implement the steps, verify, and report the results.

Frequently Asked Questions about mine-plan-exec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a MINE implementation plan?

Invoke mine-plan-exec with one plan ID or registered path, such as plan03 or P03. The Skill resolves it against the execution graph, prepares the linked worktree with mine plan prepare, starts the plan, implements the steps, verifies, commits, and marks it IMPLEMENTED.

What happens if a plan's dependencies are not accepted yet?

Execution is blocked. The Skill requires every hard predecessor to be ACCEPTED with an implementation commit and acceptance report; if the node is BLOCKED, CONDITIONAL, REJECTED, or already ACCEPTED, it reports the exact state and missing evidence instead of implementing.

Can mine-plan-exec work without the MINE MCP server?

Yes. When MCP tools are unavailable it falls back to the mine JSON CLI with --format json for graph status, plan show, prepare, start, and implemented transitions. Some operations like plan prepare and release are CLI-only by design.

Does mine-plan-exec commit directly to the stable or dev branch?

No. Implementation runs only on the MINE-managed plan/<id>-<slug> branch in a linked worktree created by mine plan prepare. It never implements on stable or dev, never force-pushes, and never rewrites shared history.

Who marks a plan as ACCEPTED after implementation?

The implementing agent only reports evidence and sets the node to IMPLEMENTED via mine_plan_mark_implemented. Acceptance requires the independent reviewer process defined by AGENTS.md, typically run through the mine-plan-review skill.