gsd-discuss-phase

Identify and discuss ambiguous areas in project phases via adaptive questioning and codebase analysis.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-discuss-phase-roycolumbia-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/roycolumbia-code/claude-global-config/tree/main/skills/_audit-disabled-20260706-1136/gsd-discuss-phase
Command: npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-discuss-phase-roycolumbia-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__context7__resolve-library-id, mcp__context7__query-docs, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the decision-making process by identifying and addressing gray areas in project planning, reducing confusion and improving project efficiency.

Core Features & Use Cases

  • Adaptive Questioning: Gather project context through interactive questioning to ensure all aspects are considered.
  • Codebase Analysis: Scout for reusable assets and patterns within the codebase.
  • Gray Area Identification: Automatically identify areas of ambiguity in the project phase.
  • User Selection: Allow users to select and discuss specific gray areas.
  • Deep Dive: Explore selected areas in-depth until resolved.
  • Decision Documentation: Create a comprehensive CONTEXT.md file to guide future research and planning.
  • Use Case: When planning a software development project, use this Skill to analyze the current phase, identify and discuss potential issues, and document decisions to ensure clarity and efficiency.

Quick Start

Load the gsd-discuss-phase Skill and provide the phase number as an argument, e.g., 'gsd-discuss-phase 2'.

Frequently Asked Questions about gsd-discuss-phase

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

FAQPage Schema
How can I identify and resolve ambiguities in software project planning?

To resolve ambiguities in project planning, this Skill uses adaptive questioning and codebase analysis to identify gray areas in a specific project phase, allowing you to discuss and resolve them comprehensively.

How do I document project planning decisions for future reference?

You document planning decisions by using this Skill to generate a comprehensive CONTEXT.md file. This context documentation captures your interactive questioning and codebase analysis results to guide future research and maintain project clarity.

What is the best way to analyze a codebase for reusable assets during project planning?

The best way to analyze a codebase for reusable assets is to use this Skill's codebase analysis feature, which scouts for existing patterns during project planning. This ensures comprehensive decision-making by integrating reusable assets into your phase discussions.

Do I need to provide a phase number to start analyzing project gray areas?

Yes, you need to provide a specific phase number as an argument to start analyzing project gray areas. Supplying the phase number focuses the adaptive questioning and codebase analysis on the correct stage of your software development project.

Can I use context documentation to streamline decision-making for future development phases?

Yes, you can use the generated CONTEXT.md context documentation to streamline decision-making for future development phases. By recording resolved gray areas and codebase analysis, this Skill preserves project planning decisions for future reference and research.

How does adaptive questioning work when exploring project planning gray areas?

Adaptive questioning works by interactively gathering project context to identify specific areas of ambiguity, then allowing you to select and deep dive into those gray areas until they are resolved. This interactive process ensures all project aspects are thoroughly considered.