Skip to content
← Back to the kit
Usage: /dwp-refine [plan]

dwp-refine

Refine an existing Deep Work Plan.

What it does

dwp-refine modifies an existing plan safely. It can add, remove, or reorder tasks while strictly preserving completed evidence, prohibiting unconfirmed criterion weakening, and recording atomic contract revisions.

Usage

/dwp-refine [plan]
/dwp-refine promote [plan]

Behavior

  1. Read plan: reads the target plan and inspects existing contract and journal history.
  2. Contract amendments: in v7 plans, contract modifications run through ledger.py amend. The revision is persisted under contracts/, an amendment event is appended to journal.ndjson, and fresh approval is recorded.
  3. Closed adaptation set: mid-run plan adaptations are restricted to five authorized operations: split, reorder, insert, change_strategy, and retry. Proposals expanding scope, permissions, or budget are rejected.
  4. Preserve evidence: completed task evidence is never altered or invalidated. Unconfirmed criterion weakening is strictly prohibited.
  5. Lite-to-Full promotion: /dwp-refine promote {plan} expands inline anchored README task records into separate numbered task files without altering task IDs or invalidating existing evidence.

Explicit migration

Existing plans keep their recorded generation when the skill pack is upgraded. Migration is never automatic. A v5 plan moves to v6 only through explicit, previewed migration (shared/migrate_v6.py). A v6 plan keeps its generation and runs unchanged; new plans use the current v7 generation, and an existing plan is never migrated implicitly.

Aliases

  • dwp:refine