requirements-engineer

To elicit and document software requirements using SWEBOK, provide project context and stakeholder information so the skill can guide analysis and generate a formal Requirements Document at requirements/REQUIREMENTS.md.

The EARS format structures software requirements into clear, unambiguous statements with explicit acceptance criteria. It enforces condition-based syntax to reduce ambiguity and ensure seamless handoff to the specifications pipeline.

To structure a requirements document with functional and nonfunctional sections, the skill classifies elicited stakeholder needs and generates a structured REQUIREMENTS.md baseline separating these categories for traceability.

Yes, this requirements elicitation skill supports audit workflows and traceability checks by applying an included audit checklist and SWEBOK v4 knowledge base to validate the requirements baseline during verification.

Yes, you can use this for stakeholder interviews and requirements validation workshops across discovery and design phases, as it applies structured prompts to guide elicitation and validate captured requirements.

A limitation of using a SWEBOK-driven requirements engineer is its basic implementation depth, meaning it provides structured templates and references for specification rather than fully automating complex stakeholder negotiations.