awa-requirements

Create or Update Requirements

Bootstrap

<tool name="read_file"> <read path=".awa/.agent/awa.core.md" required="true" error="on not found" /> <read path=".awa/rules/*.md" required="true" /> <read path=".awa/specs/ARCHITECTURE.md" required="true" error="on not found" /> <read path=".awa/.agent/schemas/REQ.schema.yaml" required="true" error="on not found" /> </tool>

User Input

${input}

You MUST consider the user input before proceeding (if not empty).

Inputs

<file type="architecture" path=".awa/specs/ARCHITECTURE.md" /> <file type="feat" path=".awa/specs/FEAT-{CODE}-{feature-name}.md" required="true" /> <file type="examples" path=".awa/specs/EXAMPLE-{CODE}-{feature-name}-{nnn}.md" required="if relevant" /> <file type="requirements" path=".awa/specs/REQ-{CODE}-{feature-name}.md" required="if relevant" /> <file type="code" required="if reverse workflow" />

Action

Create or update the requirements document(s) as specified in the instruction above, following awa conventions. Consider existing specifications before making changes.

If deriving from existing code (reverse workflow), analyze the codebase to extract implicit requirements, acceptance criteria, and behavioral expectations.

Outputs

<file path=".awa/specs/REQ-{CODE}-{feature-name}.md" />

Rules

You SHALL ensure the {CODE} matches the corresponding FEAT {CODE} for the same feature if one exists. You SHALL run awa spec codes to help choose the {CODE} extending existing one if logical. You SHALL read the corresponding FEAT document before writing requirements. You SHALL solidify requirements with respect to architecture, feature context, and existing requirements. You SHALL create set of requirements in EARS format (INCOSE-compliant) based on the feature context. You SHALL identify existing requirements to update, or new requirements to create. You SHALL consider edge cases, UX, technical constraints, success criteria. You SHOULD focus on requirements which will later be turned into a design. You SHOULD keep requirements at a manageable level of detail. You SHALL ensure requirement IDs and AC IDs follow the format defined in the traceability chain (e.g. {CODE}-{n}, {CODE}-{n}_AC-{m}, {CODE}-{n}.{p}_AC-{m}). You SHALL support reverse workflow: deriving requirements from existing code when requested. You SHALL clarify open points with user. You MAY use todos and tools as needed.