corvus-phase-0

Analyze user requests to determine if clarification is needed before discovery.

3|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-phase-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: corvus-phase-0
Source: https://github.com/NachoFLizaur/corvus/tree/main/skill/corvus-phase-0
Command: npx skills add https://github.com/NachoFLizaur/corvus --skill corvus-phase-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to clarifying ambiguous user requests before starting discovery, reducing rework and scope drift by defining a formal clarifications workflow.

Core Features & Use Cases

  • Phase-based clarification: supports Phase 0a (INITIAL CLARIFICATION) and Phase 0b (POST-DISCOVERY CLARIFICATION) with explicit goals, delegated roles, and required outputs.
  • Flow-driven decisioning: tracks statuses like REQUIREMENTS_CLEAR, QUESTIONS_NEEDED, and DISCOVERY_NEEDED to route planning steps.
  • Round-tracked discovery: includes round-based tracking to limit clarification cycles and enforce progress.
  • Use Case: Product teams or AI agents use this Skill to structure requests, ensuring precise scope before discovery begins.

Quick Start

Initiate Phase 0a by submitting the user’s request to the requirements-analyst for clarity assessment.

Frequently Asked Questions about corvus-phase-0

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

FAQPage Schema
How do I clarify ambiguous requirements before starting product discovery?

To clarify ambiguous requirements before product discovery, you can apply a phase-based clarification workflow that assesses user requests, routes statuses like REQUIREMENTS_CLEAR or QUESTIONS_NEEDED, and ensures precise scope before planning begins.

What is phase-driven flow control for requirements gathering?

Phase-driven flow control for requirements gathering is a mechanism that routes planning steps across statuses like DISCOVERY_NEEDED and QUESTIONS_NEEDED, using round-tracked iteration to limit clarification cycles and enforce progress before discovery.

How do I prevent scope drift in multi-agent discovery workflows?

You can prevent scope drift in multi-agent discovery workflows by implementing formal Phase 0a and Phase 0b clarification cycles with delegated roles and required outputs, ensuring a clear scope is established before planning progresses.

Can I limit clarification cycles to avoid endless rounds of questions?

Yes, you can limit clarification cycles using round-tracked discovery, which enforces progress by monitoring iteration rounds and routing statuses like REQUIREMENTS_CLEAR or DISCOVERY_NEEDED to prevent endless questions.

When do I need a post-discovery clarification phase?

You need a post-discovery clarification phase (Phase 0b) when initial requirements gathering leaves residual ambiguity, requiring another round of structured questions to finalize scope before planning can safely proceed.