skills.rest
RayOfSteel-DHBW
RayOfSteel-DHBWCOMMUNITY
Explore all skills by this author →
GitHub

discuss-phase

Extracts actionable decisions and ambiguities from planning discussions into CONTEXT.md.

Updated Nov 16, 2025
Search Tags:#planning#documentation#context#roadmap#phase#gray-areas#discuss
One-click install
npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill discuss-phase-rayofsteel-dhbw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discuss-phase
Source: https://github.com/RayOfSteel-DHBW/TeilAutoNeu/tree/main/.github/skills/discuss-phase
Command: npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill discuss-phase-rayofsteel-dhbw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract implementation decisions that downstream agents need. Analyze the phase to identify gray areas, discuss with user, and capture decisions for research and planning.

Core Features & Use Cases

  • Decision extraction: identify decisions that guide downstream researchers and planners.
  • Gray-area discovery: surface concrete ambiguities that affect scope and implementation.
  • Context documentation: generate a CONTEXT.md capturing phase boundary, decisions, and deferred ideas for future work.
  • Collaborative workflow: structure prompts to guide user discussions and keep scope aligned with roadmap.

Quick Start

Validate the phase against the roadmap, identify gray areas, hold focused discussions, and generate the CONTEXT.md.

Frequently Asked Questions about discuss-phase

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

FAQPage Schema
How do I extract implementation decisions for downstream planning phases?▼

To extract implementation decisions for planning, analyze roadmap-driven phases to identify gray areas, hold focused discussions, and formalize decisions. This captures actionable choices in a CONTEXT.md file for downstream agents.

What is the best way to document phase boundaries and deferred ideas for a roadmap?▼

Documenting phase boundaries and deferred ideas involves generating a persisted CONTEXT.md file. This captures concrete decisions, scope alignments, and future work ideas to ensure downstream researchers and planners stay informed.

How do I identify gray areas that affect project scope before planning?▼

Identifying gray areas requires validating the phase against the roadmap to surface concrete ambiguities affecting scope. Structured prompts then guide collaborative discussions to resolve these uncertainties before formalizing decisions.

Can I use this approach to align implementation scope with a roadmap?▼

Yes, you can align implementation scope with a roadmap by validating phase boundaries against roadmap goals. Structured prompts facilitate user discussions to resolve ambiguities and ensure scope alignment before planning.

Why do I need a CONTEXT.md file for downstream agents?▼

A CONTEXT.md file is needed to provide downstream agents with extracted implementation decisions and phase boundaries. It persists deferred ideas and collaborative discussion outcomes, ensuring accurate research and planning.

When should I not use a discuss-phase approach for project planning?▼

You should not use this approach for phases lacking a defined roadmap or when no concrete gray areas exist. It relies on validating roadmap-driven phases and facilitating user discussions to extract actionable downstream decisions.

Related Skills

Explore More Product & Management Skills→
calcosmiccalcosmic
9

phase-context-gathering

Scan codebases to produce structured CONTEXT.md with gray-area severities.

Community
Intermediate
TruCol270TruCol270
1

gsd-discuss-phase

Extract phase context and decisions into a CONTEXT.md file.

Community
Advanced
cfardevcfardev

cu-edit

Modify use case markdown files and synchronize roadmap status.

Community
Intermediate
virtenginevirtengine
17

discuss-phase

Analyze a project phase against ROADMAP.md and record decisions in CONTEXT.md.

Official
Advanced