specify-requirement

To formalize requirement changes, you analyze the evolving business intent against the current context to identify INSERT, MODIFY, DELETE, and REFER actions. This process generates structured, change-oriented requirements appended directly to your spec.md file.

The EARS style for software requirements standardizes documenting changes as system responses to specific triggers. It structures requirement descriptions to clearly define observable external behaviors and maintain traceability across spec revisions.

You automate appending requirements to spec.md by invoking the specify-requirement skill with your project context. It automatically generates change-oriented requirements and appends them, maintaining consistency across document revisions.

Yes, you can map traceability for modified and deleted requirements. The system identifies the exact change scope and impact, capturing structured traceability mappings for all required requirement actions within your spec workflow.

The best way to manage requirement change scope is analyzing business intent from a system-wide perspective. This identifies all necessary INSERT, MODIFY, DELETE, and REFER actions, capturing the full impact and observable behaviors before appending to spec.md.

Generating change-oriented requirements requires no predefined dependencies. You simply invoke the generation process with your current ARGUMENTS and project feature directory context to analyze business intent and append updates to spec.md.