gsd-discuss-phase

Extract and organize phase context decisions into CONTEXT.md for downstream agents.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-discuss-phase-ev3rlit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/ev3rlit/magam-canonical-archive/tree/main/.codex/skills/gsd-discuss-phase
Command: npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-discuss-phase-ev3rlit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gather phase context through adaptive questioning before planning to reduce back-and-forth and ensure decisions are captured in CONTEXT.md.

Core Features & Use Cases

  • Adaptive questioning cadence to surface unknowns and align stakeholders.
  • Bidirectional mapping to Codex request_user_input and Task spawning for deep-dives.
  • CONTEXT.md creation and reuse by downstream agents to guide research and planning.

Quick Start

Initiate the discuss phase with a phase number and then choose which gray areas to explore, allowing Claude to pick recommended defaults with --auto.

Frequently Asked Questions about gsd-discuss-phase

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

FAQPage Schema
How do I identify gray areas in multi-phase research workflows before planning?

Adaptive questioning surfaces gray areas by iteratively probing prior project history to choose a subset of unknowns for deep-dive, ensuring phase context decisions are captured before planning begins.

How do I generate a CONTEXT.md file from existing project state and requirements?

Generating a CONTEXT.md file involves loading prior PROJECT.md, REQUIREMENTS.md, and STATE.md history, debating gray areas through adaptive questioning, and documenting the chosen decisions for downstream agents.

What is the best way to reduce back-and-forth when gathering phase context for research planning?

Adaptive questioning cadence reduces back-and-forth by systematically surfacing unknowns and aligning stakeholders, then mapping directly to downstream tasks for deep-dives to capture clear phase context.

Can I automate gray-area selection and phase context extraction for multi-phase workflows?

Yes, you can automate gray-area selection by initiating the discuss phase with a phase number and using the auto flag to let the system pick recommended defaults for deep-dive exploration.

Do I need prior PROJECT.md and STATE.md files to start adaptive questioning for phase planning?

Yes, prior PROJECT.md, REQUIREMENTS.md, and STATE.md history must be loaded and debated to establish the phase boundary and identify gray areas for the adaptive questioning process.

How does iterative probing handle phase boundaries in multi-phase research workflows?

Iterative probing handles phase boundaries by loading existing project context, debating unknowns until a subset of gray areas is chosen, and generating a CONTEXT.md that defines the boundary for downstream agents.