ferrox-discuss-phase

Extract unresolved implementation decisions and synthesize a phase-specific CONTEXT.md.

21|9|Updated Jul 21, 2026

Search Tags:#decision making #requirements analysis #phase planning #software workflow #context extraction #interactive discussion

Ready to run

npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-discuss-phase

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity before a project phase is planned by surfacing the remaining undecided implementation choices and turning them into explicit decisions.

Core Features & Use Cases

Decision extraction: Loads prior project context and identifies what is already settled versus what still needs discussion.
Targeted discussion flow: Prompts the user only on gray areas that downstream agents need resolved.
Context handoff: Produces a phase-specific CONTEXT.md so researchers and planners can proceed without re-asking the same questions.
Use case: When a build phase has multiple plausible approaches, this Skill helps lock down the approach, constraints, and assumptions before execution begins.

Quick Start

Ask the skill to discuss phase 2 and identify the remaining implementation decisions that need user input.

Frequently Asked Questions about ferrox-discuss-phase

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

FAQPage Schema

How do I resolve unresolved implementation decisions before phase planning starts?▼

To resolve unresolved implementation decisions before phase planning, extract open questions from prior project context and interactively discuss them with stakeholders to lock down specific approaches, constraints, and assumptions for downstream agents.

What is a phase-specific CONTEXT.md file used for in software workflows?▼

A phase-specific CONTEXT.md file synthesizes reviewed project context, requirements, and state files into a single handoff document, enabling downstream researchers and planners to proceed without re-asking settled questions or encountering ambiguity.

How do I extract gray area implementation choices from existing project requirements?▼

Extract gray area implementation choices by loading prior project state files and requirements, identifying what is already settled versus what remains undecided, and prompting the user interactively only on unresolved areas that downstream agents need clarified.

Can I use interactive discussion to clarify software workflow phases with multiple plausible approaches?▼

Yes, when a build phase has multiple plausible approaches, interactive discussion clarifies the phase by surfacing remaining undecided implementation choices and turning them into explicit decisions before execution begins.

Do I need prior project context and state files before starting phase decision extraction?▼

Yes, prior project context, requirements, and state files must be reviewed before discussion to identify settled decisions and accurately extract only the remaining unresolved implementation choices requiring user input.

What is the best way to hand off locked down phase decisions to downstream agents?▼

The best way to hand off locked down phase decisions is producing a phase-specific CONTEXT.md file that synthesizes all extracted context, ensuring downstream agents can plan and research without ambiguity or re-asking questions.