proj-analyze-req

To write a requirements analysis document, this skill enforces a Step 0-5 process using a mandatory questions checklist to extract high-level requirements, user roles, and scope, outputting a formal standardized template document.

Defining project scope and clarifying stakeholder needs is achieved through multi-turn requirement gathering and structured questionnaire-based validation, ensuring functional boundaries are established before technical design begins.

Structuring multi-turn requirement gathering involves tracking progress through a central task document skeleton from Step 0 to Step 5, applying a mandatory questions checklist to reduce ambiguity and validate data needs.

Yes, you can use template-based outputs to manage requirement clarification and scope estimation, linking the formal requirements document directly to task artifacts for reproducible workflow tracking.

No, the requirements analysis process explicitly excludes technical designs, focusing solely on extracting and organizing high-level requirements, user roles, scope, and data needs for stakeholder validation.