gsd-discuss-phase

Generate a {phase_num}-CONTEXT.md file documenting implementation decisions for downstream agents.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-discuss-phase-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-discuss-phase
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-discuss-phase-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill accelerates planning by eliciting phase-specific context through adaptive questions, reducing back-and-forth and aligning assumptions before action.

Core Features & Use Cases

  • Dynamic context capture: loads prior context and stakeholders' intents to identify undecided decisions.
  • Guided gray-area handling: surfaces remaining questions for user-directed discussion and closure.
  • CONTEXT.md generation: outputs a definitive {phase_num}-CONTEXT.md with decisions to guide researchers and planners.

Quick Start

Run a discuss-phase workflow to collect decisions and generate the {phase_num}-CONTEXT.md for downstream agents.

Frequently Asked Questions about gsd-discuss-phase

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

FAQPage Schema
How do I capture planning context and lock in decisions before starting implementation?

You can capture planning context by loading prior context and stakeholders' intents to identify undecided decisions, then using adaptive questions to surface remaining gray areas for user-directed discussion and closure. This generates a definitive CONTEXT.md file.

What is a discuss-phase workflow and when do I need it for software planning?

A discuss-phase workflow accelerates planning by eliciting phase-specific context through adaptive questions, reducing back-and-forth and aligning assumptions before action. You need it when researchers and planners require locked decisions to investigate or execute downstream tasks.

How do I generate a CONTEXT.md file for downstream agents to use?

To generate a CONTEXT.md file, run a discuss-phase workflow with the required phase arguments and context sources. The deterministic process scouts relevant assets, identifies gray areas, and prints a {phase_num}-CONTEXT.md containing extracted implementation decisions.

Can I use adaptive questions to frame context for multi-phase software engineering workflows?

Yes, adaptive questions frame context for multi-phase workflows by loading prior context and identifying undecided gray areas. The process outputs a {phase_num}-CONTEXT.md for each phase, ensuring downstream researchers and planners have the locked decisions they need.

Does this context-management approach require specific dependencies or components to run?

No specific dependencies or components are required. The workflow requires phase arguments and context sources as input, then executes a deterministic process that prints the {phase_num}-CONTEXT.md file to guide downstream actions.

Why does my planning workflow fail when downstream agents misinterpret assumptions?

Planning workflows fail when assumptions are unaligned. This skill solves the problem by using adaptive questions to elicit phase-specific context, capturing stakeholder intents and locking decisions into a CONTEXT.md file to align downstream agents before action.