gsd-discuss-phase

Generate phase-specific CONTEXT.md files by resolving implementation decisions through adaptive questioning.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-discuss-phase-pear-commerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-discuss-phase
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-discuss-phase-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of incomplete or ambiguous phase implementation context that leads to flawed research, planning, and wasted development effort by systematically gathering and locking down all necessary decisions before downstream workflow steps begin.

Core Features & Use Cases

  • Adaptive Questioning: Generates phase-specific gray areas based on the phase goal and prior project context, then asks targeted questions to resolve each one.
  • Scope Guardrails: Prevents scope creep by redirecting new feature ideas to deferred ideas instead of adding them to the current phase.
  • Structured Context Output: Creates a standardized {phase_num}-CONTEXT.md file with all agreed-upon decisions that downstream research and planning agents can use without additional user input.
  • Use Case: When starting a new implementation phase for a software feature, use this Skill to resolve all open implementation questions (e.g., layout for user-facing components, error response formats) before the planning agent generates the phase roadmap.

Quick Start

Use the gsd-discuss-phase skill with your target phase number to gather all required implementation context and create a structured CONTEXT.md file for downstream planning 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 gather implementation context before planning a software project phase?

Gathering implementation context requires adaptive questioning to resolve open decisions before planning. This skill generates phase-specific questions based on project goals and outputs a structured CONTEXT.md file to lock down decisions for downstream agents.

Why does incomplete phase context cause planning errors in development workflows?

Incomplete phase context causes planning errors because unresolved implementation decisions lead to flawed research and wasted effort. Locking down all ambiguous requirements into a structured context file eliminates redundant user input during subsequent workflow steps.

What's the best way to prevent scope creep when discussing project phase requirements?

Preventing scope creep during phase discussions involves redirecting new feature ideas to a deferred list instead of adding them to the current phase. This keeps the implementation scope locked while capturing ideas for future use.

How do I resolve open implementation decisions before generating a phase roadmap?

Resolving open implementation decisions before roadmap generation involves adaptive questioning about gray areas like component layouts or error formats. Agreed decisions are captured in a CONTEXT.md file for the planning agent to consume without additional input.

Do I need a structured context file to automate downstream software planning?

A structured context file is needed to automate downstream planning because it captures all agreed-upon decisions. This standardized output allows research and planning agents to execute without requiring redundant user input during the workflow.

When should I use adaptive questioning for software project planning?

Adaptive questioning for project planning should be used when starting a new implementation phase. It identifies phase-specific gray areas based on goals and prior context to systematically resolve all unresolved implementation decisions before execution begins.