skills.rest
dobrinz123
dobrinz123COMMUNITY
Explore all skills by this author →
GitHub

gsd-discuss-phase

Extract implementation decisions and phase context into a phase-specific CONTEXT.md artifact.

Updated Apr 9, 2026
Search Tags:#codebase-analysis#phase-planning#decision-capture#context-gathering#project-workflow#user-interaction#context.md
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-discuss-phase-dobrinz123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-discuss-phase
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-discuss-phase-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity during project phase handoffs by extracting and documenting the implementation decisions that downstream researchers and planners need to proceed without re-asking the user. It centralizes prior context, identifies unresolved "gray areas", and converts interactive discussions into a concrete CONTEXT.md artifact for the next workflow steps.

Core Features & Use Cases

  • Prior context loading: Automatically reads PROJECT.md, REQUIREMENTS.md, STATE.md and any existing CONTEXT.md files to avoid re-asking settled questions.
  • Codebase scouting: Searches the repository for reusable assets, patterns, and technical constraints that affect phase choices.
  • Adaptive questioning: Presents detected gray areas for user selection and performs deep dives until decisions are finalized.
  • Deliverable: Produces a {phase_num}-CONTEXT.md that captures concrete implementation decisions so researchers and planners can act autonomously.
  • Use Case: Prepare a new frontend phase by resolving API contracts, shared component reuse, and deployment constraints before writing a detailed plan.

Quick Start

Ask gsd-discuss-phase to analyze phase 2 and produce 2-CONTEXT.md that records resolved implementation decisions and unanswered questions for downstream planning.

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 implementation decisions before starting a software project phase?▼

To capture implementation decisions before a project phase, you need to load prior context from PROJECT.md and REQUIREMENTS.md, scout the codebase for constraints, and resolve gray areas interactively to produce a CONTEXT.md artifact for downstream planning.

What is phase context gathering and why is it needed for codebase analysis?▼

Phase context gathering is the process of extracting unresolved technical gray areas and prior decisions from project state files. It is needed to prevent downstream research agents from re-asking settled questions during codebase analysis.

How do I generate a CONTEXT.md file for downstream planning agents?▼

You generate a CONTEXT.md file by applying an interactive workflow that reads STATE.md, scans the repository for reusable assets, asks adaptive questions to finalize decisions, and writes the resolved choices into a phase-specific artifact.

Do I need specific markdown files to start resolving project phase gray areas?▼

Yes, resolving project phase gray areas requires read access to PROJECT.md, REQUIREMENTS.md, and STATE.md. These files provide the prior context necessary to identify unresolved decisions without re-asking settled questions.

What's the best way to document API contracts and deployment constraints before planning?▼

The best way to document API contracts and deployment constraints is through interactive clarification that detects gray areas, performs deep dives until finalized, and records the resolved implementation decisions in a structured CONTEXT.md file.

Why does my planning agent keep re-asking settled questions during phase handoffs?▼

Planning agents re-ask settled questions during phase handoffs when prior context is not centralized. Loading existing PROJECT.md and STATE.md files and generating a phase-specific CONTEXT.md artifact prevents this ambiguity.

Related Skills

Explore More Software Engineering Skills→
D0NMEGAD0NMEGA
8

gsd-discuss-phase

Gather phase context through adaptive questioning and output CONTEXT.md.

Community
Advanced
diShine-digital-agencydiShine-digital-agency
1

shine-discuss-phase

Extract implementation decisions from project context into CONTEXT.md.

Community
Advanced
wyattjohwyattjoh
1

research-augmented-design

Verify technical hypotheses and API constraints with parallel background research agents.

Community
Advanced
CodeAlexxCodeAlexx
1

coder:discuss-phase

Capture phase implementation decisions and generate a CONTEXT.md file.

Community
Intermediate