mine-plan-create

Creates evidence-backed implementation plans registered in a MINE execution graph.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning accepted architecture into work that independent coding agents can execute is hard: plans are often vague, ignore existing design decisions, skip external research, or conflict with parallel workstreams. This Skill produces precise, executable implementation plans grounded in repository evidence, accepted Design documents, and verified external sources, then registers them in a dependency-aware execution graph. ## Core Features & Use Cases - Scope-first planning: An explicit user scope defines the planning boundary, keeping repository inspection and research proportional to the requested work. - Mandatory external research: Every substantive plan requires opened, authoritative web sources recorded in a research register tied to concrete decisions. - Execution graph integration: Plans are registered via MINE MCP tools or the JSON CLI, released from DRAFT to READY or BLOCKED, and validated against the graph. - Parallel execution design: Work packages get disjoint write scopes, serial owners for shared files, and a parallel execution protocol when lanes run concurrently. - Use Case: After mine-arch accepts a design for session storage, invoke this Skill with that scope to produce a numbered plan under docs/plan/ with work packages, verification matrices, and a registered graph node ready for mine-plan-exec. ## Quick Start Ask the agent to create an implementation plan for a specific scoped feature or change, for example: create a MINE plan for adding session storage and recovery based on the accepted design.

Frequently Asked Questions about mine-plan-create

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

FAQPage Schema
How do I create an implementation plan from an accepted design?

Invoke the Skill with an explicit scope naming the requirement or design change. It inspects the governing design leaves, gathers proportional repository evidence, performs mandatory web research, writes a plan under docs/plan/, and registers it in the execution graph.

What is the MINE execution graph and how are plans registered?

The execution graph is a TOML-based dependency tracker in docs/plan/ managed by the mine binary. Plans are added as DRAFT nodes via mine_plan_add or the JSON CLI, then released to READY or BLOCKED with the CLI-only mine plan release command.

Does this Skill work without the MINE MCP server?

Yes. When MCP tools are unavailable, it falls back to the mine --format json CLI commands. Release and withdraw operations are CLI-only regardless, since no MCP tool exposes those lifecycle transitions.

When should a planning decision go back to architecture instead?

When planning reveals a material gap affecting product behavior, public APIs, data semantics, security boundaries, or deployment topology, that portion stops and routes back to mine-arch. The plan never silently overrides accepted Design.

Why does plan creation require web research?

Substantive planning must compare established practice using opened authoritative sources like official documentation and standards. Each source is recorded in a research register tied to a specific plan decision, preventing closed-world design and uninvented local mechanisms.

Can multiple agents execute plans in parallel safely?

Yes, when the plan defines parallel lanes with disjoint write scopes and a parallel execution protocol. Shared files like lockfiles and migrations get a single serial owner, and join gates verify integration.