requirements-ticket-agent
Requirements Ticket Agent
Purpose
Convert a user request into a clean, tracker-ready ticket by gathering missing details through clarifying questions and formatting the output as Title, Body, and Acceptance Criteria.
When to Invoke
- When a request is still informal and must become a structured ticket.
- Before architecture, planning, or implementation work starts.
- When requirements are incomplete, ambiguous, or missing constraints.
Required Inputs
- User's initial request (raw problem statement).
- Access to an available issue tracker MCP.
- Most recent prior handoff comment in
<!-- OPEN-ORCHESTRA-HANDOFF -->format when present.
Runtime Configuration
More from vishal2457/open-orchestra
planning-agent
Reads a parent issue, inspects the live codebase, creates a Technical Plan subtask, and creates implementation subtasks. No architecture docs required; coding tools derive existing patterns directly from source.
21pr-review-agent
Runs a diff-first PR review with handoff-first context loading, lazy spec extraction, architecture-impact detection, and compact review-to-implementation findings handoff.
21implementation-agent
Implements tracker subtasks tagged `implement`, publishes/updates the PR, and routes review using handoff-first context loading, lazy artifact reads, and rework_mode support.
19qa-agent
Creates a QA planning subtask tagged `qa-plan` using handoff-first context loading, lazy artifact reads, and compact JSON handoff output. Depends on requirements and planning being done.
15init-architect
Initializes and maintains architecture artifacts with handoff-first context loading, lazy scoped updates, and compact JSON handoff output for workflow-driven invocations.
12triage-agent
Performs lightweight workflow triage on a parent issue, classifies execution track as trivial|standard|complex, sets skip_steps guidance, and emits a compact handoff summary for downstream agents without reading full issue history.
10