gsd-cc-discuss

Identify gray areas in a slice and generate CONTEXT.md with decisions.

3|Updated Mar 23, 2026

Search Tags:#planning #context #stakeholder #decision-record #discuss #gsd-cc

Ready to run

npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-discuss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-cc-discuss
Source: https://github.com/0ui-labs/GSD-CC/tree/main/gsd-cc/skills/discuss
Command: npx skills add https://github.com/0ui-labs/GSD-CC --skill gsd-cc-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-planning discussion helps identify gray areas in the current slice, captures implementation decisions, and writes CONTEXT.md to guide the plan. Use when /gsd-cc routes here, when user says /gsd-cc-discuss, or before planning a slice that has ambiguous requirements.

Core Features & Use Cases

Identify ambiguities early in the planning process and surface decisions that need to be recorded.
Capture implementation choices, constraints, and rationale to inform the next planning steps.
Write CONTEXT.md to document the debate and decisions for traceability.

Quick Start

Run /gsd-cc discuss to surface ambiguities and generate CONTEXT.md for the current slice.

Frequently Asked Questions about gsd-cc-discuss

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

FAQPage Schema

How do I clarify ambiguous requirements before planning a development slice?▼

To clarify ambiguous requirements before planning, identify gray areas across state, planning, data, and tools, then document each decision with rationale in a CONTEXT.md file. This ensures a formal record of decisions to guide the next planning steps.

What is a decision record and when do I need one for pre-planning?▼

A decision record captures implementation choices, constraints, and rationale during pre-planning. You need one when a route or slice has unclear requirements, ensuring a formal traceable record of decisions is written to CONTEXT.md before planning proceeds.

How do I document implementation decisions and rationale for traceability?▼

You document implementation decisions and rationale by loading context from state files and writing a CONTEXT.md file. This captures the debate and concrete decisions, providing traceability for stakeholders during the planning process.

Does capturing stakeholder context help surface ambiguities in planning?▼

Yes, capturing stakeholder context helps surface ambiguities by loading context from state files to identify gray areas in the current slice. This ensures implementation decisions and constraints are recorded with rationale in CONTEXT.md.

What's the best way to generate a CONTEXT.md file for a project slice?▼

The best way to generate a CONTEXT.md file is to run a pre-planning discussion that identifies gray areas across state, planning, data, and tools, then writes concrete decisions with rationale to the file for the current slice.