gpd-revise-phase

Supersede completed research phases and create replacement phases with inherited context.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-revise-phase-michaelsengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-revise-phase
Source: https://github.com/MichaelsEngineering/get-physics-done-test/tree/main/.agents/skills/gpd-revise-phase
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-revise-phase-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to supersede a completed research phase and create a replacement that preserves historical context and updates artifacts, decisions, and roadmaps.

Core Features & Use Cases

  • Supersede completed phases without deleting artifacts to preserve historical records.
  • Create a replacement decimal-phase (e.g., 3.1) that inherits valid context and updates downstream references.
  • Update ROADMAP.md, STATE.md, and related artifacts to reflect the supersession and new phase.
  • Document the supersession in SUPERSEDED.md for auditability and reproducibility.

Quick Start

Run the revise-phase workflow for the target phase with a reason.

Frequently Asked Questions about gpd-revise-phase

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

FAQPage Schema
How do I revise a completed research phase without losing historical context?

To revise a completed research phase without losing history, supersede the original phase and generate a decimal replacement that inherits valid context while updating decisions, artifacts, and downstream references.

What is the best way to update downstream references when superseding a workflow phase?

Updating downstream references during phase supersession requires recording the change in state and ROADMAP artifacts, ensuring the replacement phase inherits context while adjusting subsequent plans across the research workflow.

When do I need to create a decimal replacement phase in a non-linear research workflow?

You need to create a decimal replacement phase when later insights require revisiting earlier completed phases, allowing you to adjust downstream plans while preserving the original artifacts for auditability and reproducibility.

Does superseding a completed phase delete the original artifacts and records?

Superseding a completed phase does not delete original artifacts; it marks the phase as superseded and documents the action in SUPERSEDED.md to preserve historical records for auditability and traceability.

How do I document phase supersession for auditability in research workflows?

Documenting phase supersession for auditability involves recording the reason for the change, marking the original phase superseded, and logging the transition in SUPERSEDED.md alongside updated STATE.md and ROADMAP.md artifacts.

Can I update ROADMAP.md and STATE.md artifacts when replacing a superseded phase?

You can update ROADMAP.md and STATE.md artifacts when replacing a superseded phase, as the workflow automatically reflects the supersession and generates a replacement phase with inherited context to align downstream plans.