1.7 KiB
allowed-tools, argument-hint, description
| allowed-tools | argument-hint | description |
|---|---|---|
| Task(*), Read(*), Glob(*) | <ticket-path | prompt> [research.md] | Create requirements.md with testable acceptance criteria from a ticket or prompt |
Execute requirements analysis for: $ARGUMENTS
Step 0: Parse Arguments and Determine Context
- Parse $ARGUMENTS to extract:
- Primary argument: Either a ticket file path (e.g., ticket.md) OR a direct text prompt
- Optional second argument: research.md path
- Determine if first argument is a file path or prompt:
- If it ends with .md or contains path separators, treat as file path
- Otherwise, treat as direct prompt text
- If file path: Get the directory path where the ticket file is located
- If prompt: Use current working directory as output location
- This directory will be used as the output location for requirements.md
- Check if research.md was provided as second argument
Step 1: Requirements Analysis Launch the requirements-analyzer agent:
Source: [ticket path from $ARGUMENTS OR direct prompt text] Research file: [research.md path if provided as second argument] Output directory: [Same directory as ticket file OR current working directory] Output filename: requirements.md (not spec.md) Task: Analyze requirements and create requirements.md with testable acceptance criteria. If research.md is provided, use it to inform requirements based on existing implementation patterns. If source is a direct prompt, use it as the requirements input.
Expected Output: ✅ requirements.md with acceptance criteria in the target directory
Next Steps: After requirements.md is created, you can:
- Run
/test-scenarios <directory>to generate detailed test scenarios - Or continue with the full workflow using
/create-design <directory>