gsd-discuss

Ask clarifying questions one at a time to lock assumptions in CONTEXT.md.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-discuss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-discuss
Source: https://github.com/alo-exp/silver-bullet/tree/main/skills/gsd-discuss
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adaptive questioning to surface assumptions and lock decisions before planning in GSD-driven projects.

Core Features & Use Cases

  • Read Phase Context and Requirements for phase goals and relevant REQ-IDs.
  • Ask Clarifying Questions one at a time, waiting for each answer before the next.
  • Lock Decisions by updating CONTEXT.md and gating progress until decisions exist.
  • Gate exits to ensure all gray areas are resolved before proceeding to planning.

Quick Start

Describe your ambiguous phase, then let the skill guide one-question-at-a-time clarifications until decisions are locked.

Frequently Asked Questions about gsd-discuss

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

FAQPage Schema
How do I clarify ambiguous requirements before planning a software project?

To clarify ambiguous requirements before planning, you can iteratively ask clarifying questions one at a time to surface gray areas and lock decisions. This ensures all critical assumptions are resolved before project planning begins.

What is the best way to surface and lock assumptions in a project planning phase?

The best way to surface and lock assumptions is by using adaptive questioning to identify gray areas, then writing locked decisions to CONTEXT.md. This gates progress and prevents exiting the phase until all decisions have resolved entries.

How do I prevent moving to the planning phase with unresolved project assumptions?

You prevent moving to planning with unresolved assumptions by enforcing gating logic that blocks phase exits. The system requires all gray areas to have resolved decisions written to CONTEXT.md before proceeding.

Can I use a gating mechanism to ensure all decisions are locked before planning?

Yes, you can use a gating mechanism to ensure decisions are locked by updating CONTEXT.md with resolved entries. This mechanism blocks progress until every gray area identified through clarifying questions has a locked decision.

How does asking clarifying questions one at a time improve context management?

Asking clarifying questions one at a time improves context management by systematically surfacing assumptions and waiting for each answer before proceeding. This enforces structured resolution of gray areas before locking decisions in CONTEXT.md.

When do I need to resolve gray areas before starting the planning phase?

You need to resolve gray areas before starting the planning phase whenever your project requirements are ambiguous. Identifying and locking critical assumptions through clarifying questions ensures a solid context foundation for planning.