coder:discuss-phase

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

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/CodeAlexx/Eri-Rpg --skill coder-discuss-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coder:discuss-phase
Source: https://github.com/CodeAlexx/Eri-Rpg/tree/main/erirpg/skills/coder-discuss-phase
Command: npx skills add https://github.com/CodeAlexx/Eri-Rpg --skill coder-discuss-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and organize critical decisions for a specific phase before planning to ensure consistent downstream context and avoid scope creep.

Core Features & Use Cases

  • Gray-area discovery: Identify ambiguities in the phase that would alter implementation.
  • Decision capture: Translate discussions into a CONTEXT.md with phase boundary and decisions.
  • Context readiness: Provide a ready-to-plan CONTEXT.md for downstream agents and planners.

Quick Start

Analyze phase X using the discuss-phase workflow to begin collecting decisions and generate CONTEXT.md.

Frequently Asked Questions about coder:discuss-phase

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

FAQPage Schema
How do I capture implementation decisions before phase planning to prevent scope creep?

Capturing implementation decisions involves analyzing a phase to identify gray areas, choosing which to discuss, and producing a CONTEXT.md. This provides a ready-to-plan context for downstream planners and prevents scope creep.

What is a CONTEXT.md file used for in a planning workflow?

A CONTEXT.md file defines phase boundaries and captured decisions to provide ready-to-plan context for downstream agents and planners. It is committed alongside a decision summary to guide consistent implementation.

How do I identify gray areas in a software development phase before implementation?

To identify gray areas, analyze the phase to spot ambiguities that would alter implementation. You then choose specific areas to discuss and translate those decisions into a structured context file.

Does the discuss-phase workflow require the erirpg CLI to validate phases?

Yes, the workflow integrates with the erirpg CLI to validate the phase, manage context files, and commit the ready-to-plan CONTEXT.md along with a summary of decisions.

When should I use decision-capture workflows for phase planning?

Use decision-capture workflows when a phase contains ambiguities that risk altering implementation. Capturing these decisions early ensures consistent downstream context and avoids scope creep during planning.