gpd-discuss-phase

Extract phase-specific decisions and generate CONTEXT.md for downstream GPD researchers.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-discuss-phase
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-discuss-phase
Source: https://github.com/CharlieGreenman/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-discuss-phase
Command: npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-discuss-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gather phase context by identifying gray areas, prompting user discussions, and producing a CONTEXT.md that guides researchers and planners. The workflow ensures decisions are captured, referenced anchors preserved, and deferred ideas tracked for future phases.

Core Features & Use Cases

  • Adaptive Socratic questioning to surface methodological decisions.
  • Automated generation of CONTEXT.md with decisions, assumptions, and anchors.
  • Support for downstream agents: gpd-phase-researcher and gpd-planner to focus literature tasks and planning.
  • Preservation of user-provided observables, deliverables, references, and stop conditions across phases.

Quick Start

Initiate a phase discussion by running the gpd CLI for the desired phase to begin extracting decisions and generate CONTEXT.md.

Frequently Asked Questions about gpd-discuss-phase

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

FAQPage Schema
How do I capture phase decisions and track deferred ideas for research planning?▼

Capture phase decisions by applying adaptive Socratic questioning to identify gray areas, then generate a CONTEXT.md file to document decisions, assumptions, and anchors while tracking deferred ideas for future phases.

What is the best way to generate audit-ready context with explicit assumptions for research workflows?▼

Generate audit-ready context by extracting phase-specific decisions through Socratic dialogue, preserving referenced anchors, and producing a structured CONTEXT.md that outlines explicit assumptions, limits, and actionable next steps.

How do I identify gray areas in project phases before passing context to downstream researchers?▼

Identify gray areas by initiating Socratic dialogue within the phase discussion, prompting user conversations to surface methodological decisions, and automatically logging them into a CONTEXT.md for downstream agents.

Can I use adaptive questioning to preserve user-provided observables and stop conditions across phases?▼

Adaptive questioning preserves user-provided observables, deliverables, references, and stop conditions by extracting them during the phase discussion and documenting them within the generated CONTEXT.md.

How do I start extracting decisions and generating context for ROADMAP-defined phases?▼

Start extracting decisions by running the gpd CLI for the desired ROADMAP-defined phase, which initiates the discussion to surface methodological choices and generate the required CONTEXT.md file.

Do I need a predefined ROADMAP to begin phase planning and decision capture?▼

A predefined ROADMAP is required because the decision capture process extracts phase-specific decisions and carry-forward guidance specifically from ROADMAP-defined phases to feed downstream researchers and planners.