القائمة
Conversational demand clarification and feasibility research before formal work item registration
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Register work items, create feature branches, track and advance stages, close work items in the VibeFlow docs-first development workflow
Codebase discovery and analysis for Stage B of the VibeFlow docs-first workflow
Create Feature Specs for Stage E of the VibeFlow docs-first workflow
Create PRDs with success metrics for Stage A of the VibeFlow docs-first workflow
Create tech specs with architecture for Stage C of the VibeFlow docs-first workflow
Release preparation for Stages I-L of the VibeFlow docs-first workflow
| name | clarify-demand |
| description | Conversational demand clarification and feasibility research before formal work item registration |
| metadata | {"triggers":["intake","new idea","I want to build","explore feasibility","should I build","assess feature","pre-register"]} |
Conversational demand clarification and feasibility research before formal work item registration.
This skill helps users go from a vague idea to a concrete work item registration. It runs before /manage-work register to ensure the right track, scope, and description are chosen.
Works on any branch (including main).
Ask the user to clarify the following (skip items they've already provided):
Keep the conversation natural. Ask follow-up questions if answers are vague. One or two rounds is usually enough.
Perform read-only codebase analysis:
Skip this phase for obvious Micro/Small items where the scope is clear and the change is localized.
Produce an Intake Brief (displayed in conversation, not persisted to disk):
## Intake Brief
**Problem**: [1-2 sentences]
**Users**: [who benefits]
**Feasibility**: [summary from Phase 2, or "Skipped — scope is clear"]
**Complexity**: [Low / Medium / High]
**Recommended Track**: [Micro / Small / Medium / Large]
**Rationale**: [why this track]
**Suggested Description**: "<description for register command>"
**Suggested ID**: <numeric ID>
Present the Intake Brief to the user. If they confirm:
/manage-work register "<description>" <ID> <track>
If they want changes, loop back to the relevant phase.