gsd-discuss-phase

Gather software development phase context through adaptive questioning and create a CONTEXT.md document.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-discuss-phase-zerada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/zerAda/RestaurantAgentAutomation/tree/main/.agent/skills/gsd-discuss-phase
Command: npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-discuss-phase-zerada

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in streamlining the decision-making process by gathering phase context through adaptive questioning before planning, ensuring that downstream agents have the necessary information without repeated inquiries.

Core Features & Use Cases

  • Adaptive Questioning: Gather phase context by asking relevant questions tailored to the situation.
  • Automated Analysis: Analyze the codebase for reusable assets and patterns to identify gray areas.
  • User Interaction: Present identified areas for discussion and allow user selection.
  • Context Documentation: Create a CONTEXT.md file documenting decisions for future reference.
  • Use Case: Ideal for software development to ensure that all team members are aligned before proceeding to the next phase.

Quick Start

Run the skill with the phase number you wish to analyze, e.g., 'gsd-discuss-phase 3'.

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 context for software development phases to improve decision-making?

You can streamline decision-making by using a tool that gathers phase context through adaptive questioning. It analyzes the codebase for reusable patterns, presents gray areas for discussion, and outputs a CONTEXT.md document to align team members before proceeding.

What's the best way to document software development decisions for future reference?

The best way to document decisions is by generating a CONTEXT.md file. The tool analyzes your codebase for reusable assets and patterns, asks tailored questions to clarify gray areas, and records the resulting decisions for future reference.

How do I analyze a codebase for reusable assets before planning the next development phase?

Analyzing a codebase for reusable assets is handled automatically during phase context gathering. The tool scans your project to identify existing patterns and gray areas, then presents these findings through user interaction to ensure all team members are aligned before planning proceeds.

Do I need workflow files and templates to use this code analysis and phase management tool?

Yes, workflow files and templates are required dependencies to execute this phase context gathering tool. They are necessary for the adaptive questioning process and to properly generate the final CONTEXT.md documentation for your software development phase.

How to start gathering phase context using adaptive questioning?

To start gathering phase context, run the tool with the specific phase number you wish to analyze, such as 'gsd-discuss-phase 3'. The system will then initiate adaptive questioning and codebase analysis to identify reusable assets and gray areas for team discussion.