shine-discuss-phase

Name: shine-discuss-phase
Availability: InStock
Author: diShine

Extract implementation decisions from project context into CONTEXT.md.

1|Updated Apr 15, 2026

Search Tags:#automation #workflow #planning #research #context #decision-making #context.md

Ready to run

npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-discuss-phase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shine-discuss-phase
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-discuss-phase
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-discuss-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and lock decisions and context gathered during the discuss phase to enable researchers and planners to act without repeating questions, ensuring continuity across cycles.

Core Features & Use Cases

Load and consolidate prior context (PROJECT.md, REQUIREMENTS.md, STATE.md, and previous CONTEXT.md) to anchor decisions.
Surface undecided areas through adaptive questioning and targeted exploration.
Output a concrete CONTEXT.md with actionable decisions to guide downstream agents and future workflow steps.

Quick Start

Run the discuss-phase workflow to generate a decisions-first CONTEXT.md for the next planning steps.

Frequently Asked Questions about shine-discuss-phase

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

FAQPage Schema

What is a discuss phase workflow for project planning and decision-making?▼

Adaptive questioning in project planning surveys the codebase for reusable patterns and surfaces undecided areas for deeper analysis. It targets specific implementation gaps rather than asking generic questions, ensuring context gathering remains focused and actionable.

How do I consolidate project context from multiple markdown files like PROJECT.md and REQUIREMENTS.md?▼

Generating a CONTEXT.md file involves loading prior project context, surveying the codebase for reusable patterns, and applying adaptive questioning to surface undecided areas. The output provides clear, actionable decisions that guide research, planning, and future workflow steps.

Do I need prior context files like STATE.md before running the discuss phase workflow?▼

How does adaptive questioning surface undecided areas in a codebase for research and planning?▼

You can consolidate project context by loading prior markdown files including PROJECT.md, REQUIREMENTS.md, STATE.md, and previous CONTEXT.md. This anchors implementation decisions and ensures continuity across workflow cycles without repeating questions.

What is the best way to extract implementation decisions for downstream researchers and planners?▼

The best way to extract implementation decisions is to run a discuss phase workflow that loads prior context, surveys reusable codebase patterns, and outputs a concrete CONTEXT.md. This ensures researchers and planners can act without repeating questions.

Why does my project context break down across workflow cycles without a dedicated decisions file?▼

Project context breaks down when implementation decisions are not locked into a dedicated file like CONTEXT.md. Without consolidating prior state and surfacing undecided areas, downstream agents must repeat questions, disrupting continuity and planning.