gsd-discuss-phase

Collect phase context and implementation decisions into a CONTEXT.md file.

264|11|Updated Apr 25, 2026

Search Tags:#workflow #planning #context #requirements #discussion #phase

Ready to run

npx skills add https://github.com/coco-research/coco --skill gsd-discuss-phase-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-discuss-phase
Command: npx skills add https://github.com/coco-research/coco --skill gsd-discuss-phase-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams resolve ambiguous implementation decisions before planning so downstream work can proceed with clear scope, fewer re-questions, and better coordination.

Core Features & Use Cases

Context Gathering: Loads prior project context and identifies what is already decided versus still open.
Adaptive Questioning: Narrows gray areas through targeted discussion instead of broad, repetitive interviews.
Decision Capture: Produces a phase-specific context file that records settled choices for researchers and planners.
Use Case: A software team preparing a new phase can use this Skill to clarify architecture constraints, workflow choices, and dependencies before execution starts.

Quick Start

Ask the skill to discuss the current phase and answer its prompts so it can produce a context file with the remaining decisions.

Frequently Asked Questions about gsd-discuss-phase

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

FAQPage Schema

How do I clarify ambiguous implementation decisions before planning a software project phase?▼

To clarify implementation decisions before planning, use adaptive questioning to resolve gray areas. This approach loads prior project context, distinguishes settled choices from open questions, and generates a context file for downstream execution.

What is the best way to capture phase context and requirements for downstream agents?▼

Capturing phase context requires generating a CONTEXT.md file that records settled choices. This file passes phase-specific implementation decisions to downstream agents, allowing them to execute planning without re-asking the user repetitive questions.

How do I stop downstream agents from re-asking the same project questions during planning?▼

To stop downstream agents from re-asking questions, produce a phase-specific context file. By resolving gray areas and recording implementation decisions upfront, downstream planners can load reusable context without requiring user interviews.

Does this discussion workflow require prior project state inspection before generating context?▼

Yes, this discussion workflow requires prior project state inspection. The process selectively deep dives into existing project context to identify settled architecture constraints and dependencies before generating the final context file.

When do I need adaptive questioning for software project planning discussions?▼

You need adaptive questioning for software project planning when resolving gray areas across discussion and planning workflows. It targets specific unresolved implementation decisions rather than conducting broad, repetitive interviews with the team.

Can I use this context gathering workflow for architecture constraints and dependencies?▼

Yes, you can use this context gathering workflow for architecture constraints and dependencies. It collects phase-specific context and resolves these implementation decisions so downstream work proceeds with clear scope.