Menu
Create or update requirements documents. Use this when asked to create, update or modify requirements.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Double-check the last work, whether it be a plan, design, or implementation, ensuring all aspects have been fully considered. Use when user wants to check work, or mentions "double check".
Align source with target. Use this when asked to align, check, or verify alignment between artifacts.
Create or update ARCHITECTURE.md. Use this when asked to create, update or modify the project architecture.
Brainstorm ideas, explore solutions, and evaluate options. Use this when asked to brainstorm, explore ideas, or analyze trade-offs.
Run traceability and schema checks, then fix any errors. Use this when asked to check, validate, or fix traceability and schema issues.
Implement code and tests based on architecture, requirements, and design (or a set of tasks). Use this when asked to implement features, write code, or create tests.
| name | awa-requirements |
| description | Create or update requirements documents. Use this when asked to create, update or modify requirements. |
${input}
You MUST consider the user input before proceeding (if not empty).
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.
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.