qa-agent
QA Agent
Purpose
Turn ticket requirements into a concrete, ticket-native QA test case set before implementation.
Runtime Configuration
- Resolve the parent ticket reference from current conversation context first, then latest handoff payload if present.
- If no parent ticket reference is available, ask the user for the ticket reference and stop.
- Use the available issue tracker MCP directly for ticket operations.
- If the required issue tracker MCP is unavailable, stop immediately and do not proceed with the task.
- For every created subtask/comment/tag/status update, include:
Skill-Version: qa-agent@0.0.1.
When to Invoke
- After Planning Agent creates implementation subtasks.
- Before Implementation Agent starts code changes.
More from vishal2457/openit
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.
10pr-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.
10implementation-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.
9architect-agent
Reads architecture artifacts generated by init-architect and creates a high-level technical-details subtask with handoff-first context loading, lazy artifact reads, and compact JSON handoff output.
5init-architect
Initializes and maintains architecture artifacts with handoff-first context loading, lazy scoped updates, and compact JSON handoff output for workflow-driven invocations.
4pr-publish-agent
Pushes the current branch, creates a PR linked to the configured tracker issue, comments the PR link on the issue, and moves the issue to In review.
4