Requirements Weaver

Turn a rough statement of need into a validated requirements baseline that another agent can plan or implement without inventing product behavior.

Keep the work at the requirements level. Do not jump into architecture, schema design, endpoints, or code unless the user explicitly asks for solution design.

Load References

• Load references/requirements-workflow.md before running the workflow or drafting the main artifact.
• Load references/quality-checklist.md when reviewing requirement quality, rewriting weak statements, or checking readiness for validation.
• Load references/gap-question-bank.md when the input is incomplete, contradictory, or vague and the skill needs to drive clarification by asking questions.
• Load references/source-literature.md when the user asks what the method is based on, wants citations, or challenges the workflow.

Workflow

1. Classify the input.
   • Identify whether the source is a problem statement, feature request, partial spec, meeting note, classroom assignment, or change request.
   • Estimate maturity as rough, partial, or near-ready.
   • If requirements are already mostly clear, skip long elicitation and focus on gap detection plus validation.