discuss-phase

Name: discuss-phase
Availability: InStock
Author: VirtEngine

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

17|4|Updated Oct 8, 2021

Search Tags:#planning #research #context-management #phase-analysis #stakeholder-communication #decision-capture #gray-areas

Ready to run

npx skills add https://github.com/virtengine/virtengine --skill discuss-phase-virtengine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discuss-phase
Source: https://github.com/virtengine/virtengine/tree/main/.github/skills/discuss-phase
Command: npx skills add https://github.com/virtengine/virtengine --skill discuss-phase-virtengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture and formalize decision points, trade-offs, and gray areas encountered during a project phase, ensuring clear direction for downstream agents.

Core Features & Use Cases

Surface domain boundaries and 1-2 specific ambiguities per category (UI/UX, behavior, empty states, content) to drive focused discussion.
Facilitate structured collaboration by prioritizing decisions, deferring scope-creep ideas, and producing a ready-to-use CONTEXT.md.
Generate a clear plan path from phase analysis to context creation, enabling efficient handoffs to planning and research.

Quick Start

Provide a concise summary of the phase to discuss and run the discuss-phase workflow to surface and capture decisions.

Frequently Asked Questions about discuss-phase

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

FAQPage Schema

How do I capture phase decisions to guide downstream planning and research?▼

Capture phase decisions by analyzing the phase against ROADMAP.md to surface ambiguities across domain, UI/UX, behavior, empty states, and content, then produce a CONTEXT.md that records decisions with provenance for planners.

What is the best way to manage gray areas and scope creep during project phase analysis?▼

Manage gray areas and scope creep by enforcing scope during phase analysis and deferring off-scope ideas to a Deferred Ideas section, ensuring focused context creation and traceable next steps for downstream agents.

How does stakeholder communication and decision capture work for phase-level planning?▼

Stakeholder communication and decision capture work by surfacing 1-2 specific ambiguities per category to drive focused discussion, prioritizing decisions, and generating a ready-to-use CONTEXT.md for structured collaboration.

Can I use phase analysis to create a context file for downstream research agents?▼

Yes, you can use phase analysis to create a context file by articulating phase-level decisions and gray areas, generating a CONTEXT.md that records decisions with provenance for reuse by planning and research agents.

Do I need a ROADMAP.md file to analyze project phase ambiguities and generate context?▼

Yes, you need a ROADMAP.md file to analyze project phases, as the skill evaluates the phase against this roadmap to surface concrete, actionable ambiguities and produce a traceable context document.

When should I defer ideas instead of capturing them in the phase context document?▼

You should defer ideas when they are off-scope during phase analysis, moving them to a Deferred Ideas section to enforce scope and enable focused context creation without losing traceable track of potential future work.