gpd-revise-phase

Supersede a completed research phase and create a replacement phase.

1|Updated Mar 29, 2026

Search Tags:#dependency management #data integrity #research automation #research workflow #phase revision

Ready to run

npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-revise-phase-chargrnmn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gpd-revise-phase
Source: https://github.com/CharGrnmn/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-revise-phase
Command: npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-revise-phase-chargrnmn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows researchers to revise and replace completed research phases, ensuring continuous improvement and accuracy in their work.

Core Features & Use Cases

Phase Revision: Supersede a completed research phase and create a replacement for iterative revision.
Context Preservation: Preserves the original phase as historical record while creating a new phase that inherits valid decisions and addresses what needs to change.
Downstream Impact Analysis: Identifies and updates all downstream dependencies to reflect the changes made to the research phase.

Quick Start

To revise a completed research phase, use the gpd-revise-phase skill with the phase number and reason for revision. For example: gpd-revise-phase 3 "Sign error in vertex correction".

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 the original historical record?▼

To revise a completed research phase without losing data, you can supersede the original phase. The system preserves the completed phase as a historical record while creating a replacement phase that inherits valid decisions and addresses required changes.

What is the best way to update downstream dependencies after changing a research phase?▼

The best way to update downstream dependencies after phase revision is to use an automated workflow tool. It identifies all downstream dependencies affected by the revision and updates them automatically to reflect the changes made.

How does iterative phase revision work in an automated research workflow?▼

Iterative phase revision works by superseding a completed phase and generating a replacement phase. This mechanism ensures historical context is preserved, valid decisions are inherited, and downstream dependencies are updated for continuous research improvement.

Can I replace a specific research phase if I find a data integrity error?▼

Yes, you can replace a specific research phase if you find a data integrity error. By providing the phase number and the reason for revision, the system creates a replacement phase while preserving the original phase as a historical record.

What project context do I need to provide to supersede a research phase?▼

To supersede a research phase, you need to provide the project context, the specific phase number, and the reason for revision. The system also requires access to phase-specific files to accurately inherit valid decisions and update downstream dependencies.

When should I avoid using an automated phase revision tool?▼

You should avoid using automated phase revision if your project lacks established downstream dependencies or phase-specific files. Without proper project context and dependency tracking, the tool cannot accurately analyze the downstream impact or inherit valid prior decisions.