propose

Convert user requests into Minerva work unit proposals with approved proposal.md and scratchpad.md files.

Updated May 16, 2026
One-click install
npx skills add https://github.com/honerlaw/agent-marketplace --skill propose-honerlaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose
Source: https://github.com/honerlaw/agent-marketplace/tree/main/plugins/minerva/skills/propose
Command: npx skills add https://github.com/honerlaw/agent-marketplace --skill propose-honerlaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an open-ended feature, refactor, or investigation request into a structured Minerva work unit by collecting just enough context, stress-testing the plan, and preparing the branch + worktree with an approved proposal.

Core Features & Use Cases

  • Context-sensitive intake: infers intent from inline input or current-session history, or asks what the user wants to build.
  • Scope and decomposition guidance: detects requests that span multiple independent subsystems and pushes you to split them into separate work units.
  • 2–3 approach proposal with tradeoffs: recommends a direction, then drafts a full design and runs a plan stress-test via minerva:grill-plan.
  • Section-by-section approval workflow: presents Goal/Why/Approach/Success criteria/Open Questions and requires explicit approval before any file writes.
  • Worktree + branch and proposal generation: creates .minerva/work/<NNN-slug>/ plus proposal.md and scratchpad.md inside the worktree, after NNN collision checks and .gitignore validation for .minerva/worktrees/.
  • Post-write gate and next-step handoff: performs a self-review, writes docs on the branch, then asks the user to review before proceeding to implementation via minerva:work.

Quick Start

Run minerva:propose to brainstorm the work unit, get your plan approved section by section, and initialize the branch and proposal files for you.

Frequently Asked Questions about propose

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

FAQPage Schema
How do I convert a feature request into a structured git worktree and proposal for development?

To convert a feature request into a structured work unit, this Skill guides context intake, scopes the request, stress-tests the design, and generates an NNN-slug worktree with an approved proposal.md and scratchpad.md.

What is the best way to plan a multi-subsystem refactor without mixing git branches?

Planning a multi-subsystem refactor requires scope decomposition; this Skill detects requests spanning independent subsystems and pushes you to split them into separate Minerva work units with dedicated branches.

Does this proposal workflow require a specific git repository structure?

Yes, the proposal workflow requires a repository using Minerva's `.minerva/` discipline, including validation for `.gitignore` entries to properly manage worktrees under `.minerva/worktrees/`.

How do I stress-test a design plan before creating a feature branch?

To stress-test a design plan before branch creation, this Skill drafts 2-3 approaches with tradeoffs, recommends a direction, and applies a plan stress-test via minerva:grill-plan before writing any files.

Can I review and approve the design sections before the worktree is generated?

Yes, you can review design sections before worktree generation; the workflow presents Goal, Why, Approach, Success criteria, and Open Questions, requiring explicit section-by-section approval before any file writes occur.

What happens if an NNN-slug worktree identifier already exists?

If an NNN-slug worktree identifier already exists, the Skill performs a collision check during the setup process to prevent duplicate work units and safeguard the branch creation.