replan

Record validated divergence evidence in a Minerva work unit replan log.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents stalled work and misalignment by letting you formally update a previously approved minerva proposal when new facts, broken assumptions, or scope changes require a revised approach.

Core Features & Use Cases

  • Replan for mid-work divergence: captures what went wrong and records a revised plan without jumping straight into implementation.
  • Pre-work proposal amendment: updates an approved proposal before execution, preserving accountability and auditability.
  • Stress-tested, approval-gated revision: drafts a replan entry, stress-tests it via the grill flow, and only writes after user approval.

Quick Start

Use minerva:replan to draft and approve an updated plan for the current work unit, then append it to the unit’s replan log.

Frequently Asked Questions about replan

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

FAQPage Schema
How do I update an approved project plan when new facts break original assumptions?

To update an approved project plan when assumptions break, you record the validated divergence evidence in a replan log. This process captures what went wrong and drafts a revised approach without immediately jumping into implementation.

What is the best way to amend an approved proposal before execution starts?

Amending an approved proposal before execution requires a pre-work amendment that updates the original plan while preserving accountability. You brainstorm a revised plan triple, stress-test it, and log the changes after user approval.

How do I safely revise a work unit plan midstream without losing auditability?

To safely revise a work unit plan midstream without losing auditability, you draft a replan entry capturing the Original plan, What changed, and the New plan. This entry is stress-tested and hard-gated before being written to the replan log.

Does updating project scope mid-work require hard-gating before writing the replan log?

Yes, updating project scope mid-work requires hard-gating before writing the replan log. The system stress-tests the revised plan triple and only commits the changes to the replan.md file after explicit user approval is granted.

When should I avoid using a formal replan workflow for scope changes?

You should avoid using a formal replan workflow for scope changes when you cannot resolve the target work unit or read the necessary proposal and scratchpad context. Without this baseline data, stress-testing revised plans is not possible.

Can I update proposal success criteria during the replan process?

Yes, you can update proposal success criteria during the replan process. After drafting and stress-testing the revised plan triple, the workflow optionally updates the proposal success criteria before finalizing the replan log entry.