requirements-engineering

Requirements engineering

Help the project owner gather, document, check, agree, and manage requirements without substituting model output for stakeholder evidence or approval. Work iteratively. Do not impose elicitation, documentation, review, and alignment as a fixed phase sequence.

Every start, update, or resume ends with either a maintained requirements-engineering plan and its next ready step, or a concrete next-step guide. A plan is warranted only when the available evidence supports useful sequencing.

This skill provides guidance, not enforcement. Loading it does not install packages, contact people, approve requirements, authorize implementation, or change a project.

When to use

Use this skill for requests to:

• start requirements work for a software project or early product idea;
• update requirements after new evidence, a decision, or a scope change;
• resume interrupted requirements work from project records;
• assess whether a requirement is ready for implementation handoff;
• trace the impact of changing a source, decision, or requirement;
• prepare an interview guide, stakeholder survey, observation guide, workshop agenda, context summary, prototype feedback guide, or requirements review;
• explain requirements terminology or a technical requirements sentence in plain language.

Should trigger

• "Start requirements engineering for this empty project."
• "Resume the requirements work and show me the plans I can continue."
• "REQ-17 changed. Show the impact before updating the approved requirement."
• "Draft questions for interviewing support staff about return approvals."
• "What does system boundary mean for this project?"

Should not trigger

• "Implement REQ-17 and deploy it."
• "Fix this failing unit test."
• "Write general product marketing copy."
• "Give me legal approval for this compliance requirement."
• "Send this survey to all customers."

Requirements work may identify later implementation, but that does not authorize implementation. Route implementation, legal review, external contact, deployment, or unrelated document work to the appropriate workflow under the user's actual authorization. An explicit user implementation request is authority to assess that work in its own workflow; do not falsely say no request was made. This skill itself adds no permission and does not execute that work.