gsd-discuss-phase

Gathers missing phase context by asking targeted questions before planning.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-discuss-phase-electroheadfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-discuss-phase
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-discuss-phase-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid premature planning by first collecting the missing context, constraints, and decisions needed to move a GSD workflow forward without re-asking settled questions.

Core Features & Use Cases

  • Adaptive question gathering: Identifies the remaining gray areas in a phase and asks only the questions needed to clarify them.
  • Workflow routing: Follows the correct discuss-mode path, including assumptions-based branches and interactive fallback behavior.
  • Planning preparation: Produces phase context that downstream research and planning agents can use directly without additional clarification.
  • Use Case: A project lead can invoke this Skill at the start of a phase to surface unresolved implementation choices before writing the next context document.

Quick Start

Use the gsd-discuss-phase skill to gather the unresolved decisions for phase 2 and prepare the context for planning.

Frequently Asked Questions about gsd-discuss-phase

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

FAQPage Schema
How do I gather missing project context before starting the planning phase?

To gather missing project context before planning, use interactive phase discussions to ask targeted questions that clarify unresolved decisions and constraints. This ensures all gray areas are addressed upfront, producing phase context that downstream planning agents can use directly without re-asking settled questions.

What is workflow routing for decision capture and how does it handle unresolved project choices?

Workflow routing for decision capture directs discussions through correct paths, including assumptions-based branches and interactive fallbacks. It identifies remaining gray areas in a phase and asks only necessary questions to clarify unresolved implementation choices before producing planning context.

How do I prevent premature planning when there are still unresolved implementation choices?

To prevent premature planning, initiate a phase discussion to surface and resolve unresolved implementation choices first. By adaptively asking only questions needed to clarify remaining gray areas, you avoid writing artifacts before necessary decision context is fully loaded and prepared.

Can I use interactive questions to prepare context documents for downstream research agents?

Yes, you can use interactive question gathering to prepare context documents for downstream research agents. The process captures prior context and constraints through targeted questions, producing phase context that planning and research agents can consume directly without additional clarification.

When should I not use a guided discussion phase for project context gathering?

You should not use a guided discussion phase when all project decisions are already settled and prior context is fully loaded. If there are no remaining gray areas to clarify or unresolved implementation choices to capture, the adaptive questioning workflow will have no decisions to route or resolve.