requirements-gatherer

To gather project requirements for Drupal development, this Skill asks structured questions across categories like scope, core functionality, user roles, data needs, and integrations, then saves the details to a project state file.

Structuring software project scoping before task definition involves systematically questioning project type, UI needs, and constraints, updating a project state file, and smoothly transitioning into defining the first development task.

Structured requirements gathering ensures no critical scope details are missed by guiding users through predefined categories including core functionality, data structures, and version constraints, identifying open questions for future resolution.

Yes, you can use this requirements gatherer with an existing project state file because it contextually loads existing project status information to understand current progress and appends newly gathered requirements.

When setting up a new module, the requirements gatherer covers project type, core functionality, user roles, data structures, integrations, UI needs, and performance or version constraints.

Yes, requirements gathering handles transitions to actual development tasks by facilitating a smooth handoff to defining the first development task immediately after all gathered project requirements are confirmed.