requirements-gathering

To turn user needs into a structured JSON schema, this skill interactively elicits requirements through targeted questions and edge-case discovery, outputting a validated requirements.json artifact with ISO-formatted timestamps for project planning.

The best way to elicit stakeholder questions for requirements gathering is through an interactive session that confirms user intent, classifies workflows, and maps tasks to relevant services using project context to ensure comprehensive coverage.

Yes, you can use this to classify project context and identify services. It distinguishes among features, bugs, refactors, and migrations, then maps tasks to relevant components using project_index.json.

You generate a requirements.json artifact with strict schema validation by providing a user request; the agent then asks clarifying questions, identifies constraints, and produces the final structured JSON output.

Workflow classification types supported during requirements elicitation include features, bugs, refactors, and migrations, which guide the appropriate workflow type and subsequent ADR-style planning.

Yes, you need a project_index.json file to map tasks to relevant services. The service identification feature relies on this project context to accurately map tasks to their relevant components.