Analyze documentation requirements for a JIRA ticket. Dispatches the requirements-analyst agent. Invoked by the orchestrator.
Step skill for the docs-orchestrator pipeline. Follows the step skill contract: parse args → dispatch agent → write output.
$1 — JIRA ticket ID (required)--base-path <path> — Base output path (e.g., artifacts/proj-123)--pr <url> — PR/MR URL to include in analysis (repeatable)<base-path>/requirements/requirements.md
Extract the ticket ID, --base-path, and any --pr URLs from the args string.
Set the output path:
OUTPUT_DIR="${BASE_PATH}/requirements"
OUTPUT_FILE="${OUTPUT_DIR}/requirements.md"
mkdir -p "$OUTPUT_DIR"
You MUST use the Agent tool to invoke the requirements-analyst subagent. Do NOT read the agent's markdown file or attempt to perform the agent's work yourself — the agent has a specialized system prompt and must run as an isolated subagent.
Agent tool parameters:
subagent_type: requirements-analystdescription: Analyze requirements for <TICKET>Prompt (pass this as the prompt parameter to the Agent tool):
Analyze documentation requirements for JIRA ticket
<TICKET>.Manually-provided PR/MR URLs to include in analysis (merge with any auto-discovered URLs, dedup):
<PR_URL_1><PR_URL_2>Save your complete analysis to:
<OUTPUT_FILE>Follow your standard analysis methodology (JIRA fetch, ticket graph traversal, PR/MR analysis, web search expansion). Format the output as structured markdown for the next stage.
The PR URL bullet list is conditional — include those bullets only if PR URLs were provided. If no --pr URLs exist, omit the bullet list but keep the rest of the prompt.
After the agent completes, verify the output file exists at <OUTPUT_FILE>.
If no output file is found, report an error.