skills.rest
rkz91
rkz91COMMUNITY
Explore all skills by this author →
GitHub

gsd-discuss-phase

Generate phase-specific CONTEXT.md files with actionable decisions for downstream agents.

264|11|Updated Apr 25, 2026
Search Tags:#research#workflow-automation#phase-planning#discuss-phase#context-generation#decision-documentation
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-discuss-phase-rkz91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-discuss-phase
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-discuss-phase
Command: npx skills add https://github.com/rkz91/coco --skill gsd-discuss-phase-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract implementation decisions that downstream agents need — researcher and planner will use CONTEXT.md to know what to investigate and what choices are locked. It loads prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, prior CONTEXT.md files), scouts codebase for reusable assets and patterns, analyzes the phase to skip gray areas already decided, and surfaces remaining areas for deep dive. It outputs a phase-specific CONTEXT.md with decisions that guide research and planning for downstream agents.

Core Features & Use Cases

  • Load prior context and surface decisions to align stakeholders.
  • Scout the codebase for reusable assets and patterns to inform phase planning.
  • Identify gray areas and generate explicit CONTEXT.md decisions to guide research and planning.
  • Output a phase-specific CONTEXT.md to enable downstream agents to act without further prompting.

Quick Start

Run the discuss-phase workflow to generate the CONTEXT.md that guides research and 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 document phase planning decisions for downstream agents?▼

Phase planning decisions are documented by generating a phase-specific CONTEXT.md that extracts actionable items from prior context, skipping gray areas already decided to explicitly guide downstream research and planning.

What is the best way to identify unresolved gray areas in project phases?▼

Unresolved gray areas are identified by loading prior context files like PROJECT.md and REQUIREMENTS.md to skip decisions already made, surfacing only remaining areas requiring deep dive discussion.

How does context generation work when preparing requirements for research workflows?▼

Context generation works by loading prior project state and scouting the codebase for reusable assets, outputting a CONTEXT.md that locks implementation choices to align downstream research workflows.

Can I use existing codebase patterns to inform phase planning decisions?▼

Yes, existing codebase patterns inform phase planning. The workflow scouts the codebase for reusable assets and patterns to shape the decisions documented in the CONTEXT.md output.

Do I need prior context files to generate a CONTEXT.md for decision documentation?▼

Yes, prior context files are required. The workflow loads PROJECT.md, REQUIREMENTS.md, STATE.md, and prior CONTEXT.md files to analyze the phase and extract decisions for the output document.

Related Skills

Explore More Product & Management Skills→
giovannimnzgiovannimnz

gsd-new-project

Initialize a new project by generating a planning scaffold with PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md.

Community
Advanced
MINT-IAMINT-IA

gsd-discuss-phase

Load project documents and repository patterns to produce a phase-numbered CONTEXT.md.

Official
Advanced
CharlieGreenmanCharlieGreenman
1

gpd-remove-phase

Delete an unstarted future phase and renumber subsequent phases in gpd projects.

Community
Advanced
DuySeuDuySeu
1

gsd-discuss-phase

Generate a CONTEXT.md documenting implementation decisions and gray areas.

Community
Advanced