flow-define

Coordinate Codex, Gemini, and Claude to define feature requirements and scope.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/mhdxbilal/Ai --skill flow-define-mhdxbilal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-define
Source: https://github.com/mhdxbilal/Ai/tree/main/.claude/skills/flow-define
Command: npx skills add https://github.com/mhdxbilal/Ai --skill flow-define-mhdxbilal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and scopes cross-functional requirements by coordinating Codex, Gemini, and Claude to produce a clear problem statement and actionable definition.

Core Features & Use Cases

  • Automatic activation when a user requests requirement clarification or scoping.
  • Multi-provider orchestration (Codex, Gemini, Claude) to gather technical and business perspectives.
  • Step-by-step execution contract, context capture, and synthesis results for handoff.
  • Stores synthesis results for review and traceability across projects.

Quick Start

Provide a concise P0 user clarification, and ask Claude Octopus to run the define workflow.

Frequently Asked Questions about flow-define

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

FAQPage Schema
How do I define multi-LLM requirements for feature scoping?▼

Multi-LLM requirement definition works by coordinating Codex, Gemini, and Claude to gather technical and business perspectives, enforcing an execution contract to produce a clear problem statement and actionable scope.

What is the best way to align stakeholders during the define phase?▼

Stakeholder alignment during the define phase is achieved by capturing user vision and orchestrating multi-provider analyses to identify constraints, edge cases, and cross-functional requirements for complex projects.

How do I start the define workflow for feature scoping?▼

To start the define workflow, provide a concise P0 user clarification and request the system to run the step-by-step execution contract, which captures context and records synthesis outputs for handoff.

Can I use multi-LLM orchestration for constraint identification and edge-case analysis?▼

Yes, multi-LLM orchestration applies directly to constraint identification and edge-case analysis by gathering diverse technical and business perspectives to ensure comprehensive cross-functional scoping.

Does the define phase automatically activate when I request requirement clarification?▼

The define phase activates automatically when you request requirement clarification or scoping, initiating the multi-provider orchestration to synthesize technical and business analyses.

How are synthesis outputs stored for review and traceability across projects?▼

Synthesis outputs are recorded during the define phase and stored for review, ensuring traceability of the problem statement, constraints, and actionable definitions across complex development handoffs.