QA Task Creator
Purpose
Generate structured work tasks from QA analysis outputs, coverage gaps, spec-auditor findings, risk-analyzer results, and bug reports. Supports two usage patterns: standalone (create tasks directly from user request) and paired with qa-bug-ticket-creator (auto-create linked fix/enhancement tasks from bugs).
Dual-Use Pattern
| Mode |
Trigger |
Output |
| Standalone |
User requests task creation from description, coverage gap, or spec finding |
GitHub Issue (or Jira/Linear format) with full task details |
| Paired |
Bug ticket created by qa-bug-ticket-creator |
Linked fix task referencing the bug; optionally enhancement tasks for related improvements |
When paired: bug ticket → fix task; fix task links back to bug via GitHub issue reference (e.g., "Fixes #123").
Input Sources
| Source |
Task Type |
Example |
| Coverage gaps |
Development / QA |
"Add unit tests for AuthService.login() — 0% coverage" |
| Spec-auditor findings |
Development / Documentation |
"Implement validation per spec section 4.2" |
| Risk-analyzer output |
Development / QA |
"Add integration tests for payment flow — high risk" |
| Bug reports |
Development (fix) |
"Fix null pointer in checkout when cart is empty" |
| User request |
Any |
"Create task to refactor user API" |
Task Types
| Type |
Description |
Typical Assignee |
| Development |
Implement, fix, refactor, optimize |
Dev |
| QA |
Write tests, increase coverage, update test data |
QA |
| Documentation |
Update specs, add diagrams, API docs |
Dev/QA |
| Enhancement |
Performance, validation, UI polish |
Dev |
See references/task-types.md for templates and examples.
Output Format
Tasks follow GitHub Issue / Jira / Linear story format:
- Title — Clear, actionable (verb + object)
- Description — Context, acceptance criteria, links to source
- Labels —
task, development, qa, documentation, enhancement, component tags
- Links — Parent bug, requirement, coverage gap, or spec section
- Acceptance criteria — Testable conditions for done
Auto-Linking
Tasks automatically link to their source:
| Source |
Link Format |
| Bug |
"Fixes #123" or "Related to #123" in body; GitHub auto-links |
| Requirement |
Link to requirement doc or ticket |
| Coverage gap |
File:line reference, module name |
| Spec section |
Section reference (e.g., "Spec §4.2") |
See references/linking-patterns.md for patterns.
Integrations
| Integration |
Use |
| GitHub MCP |
Create issues, search for duplicates, link to bugs |
| qa-bug-ticket-creator |
Consume bug ticket output; create linked fix task |
| qa-coverage-analyzer |
Consume coverage gap output |
| qa-spec-writer / qa-requirements-generator |
Consume spec/requirement references |
Trigger Phrases
- "Create a task to [description]"
- "Generate fix task for bug #123"
- "Create tasks from coverage gaps in [path]"
- "Task from spec-auditor findings"
- "Linked fix task for [bug summary]"
- "Work items from risk analysis"
- "Development task for [feature/fix]"
Workflow
- Input — User request, bug ticket, coverage gap, spec finding, or risk output
- Task type — Classify as Development / QA / Documentation / Enhancement
- Content — Title, description, acceptance criteria, labels
- Links — Add references to parent bug, requirement, or source
- Duplicate check — Search existing issues for similar tasks (optional)
- Create — Create GitHub Issue via GitHub MCP; output link
Scope
Can do (autonomous):
- Create tasks from user description, bug tickets, coverage gaps, spec findings
- Classify task type and assign appropriate labels
- Link tasks to parent bugs, requirements, coverage gaps
- Create GitHub Issues via GitHub MCP
- Search for duplicate tasks before creating
- Work paired with qa-bug-ticket-creator for linked fix tasks
Cannot do (requires confirmation):
- Assign to specific users without approval
- Set milestones or due dates without user input
- Create tasks in Jira/Linear (reference format only; adapters future)
Will not do (out of scope):
- Execute development or testing work
- Modify code or configurations
- Approve or prioritize tasks (stakeholder responsibility)
Quality Checklist
Troubleshooting
| Symptom |
Likely Cause |
Fix |
| Task too vague |
Insufficient context from source |
Add explicit acceptance criteria; request clarification |
| Missing link to bug |
Bug ticket not passed or not found |
Verify bug exists; include bug number in description |
| Wrong task type |
Misclassification of input |
Use references/task-types.md; ask user to confirm |
| Duplicate created |
Search query too narrow |
Broaden search terms; check similar open issues |
| GitHub MCP fails |
Token missing, repo access |
Verify GitHub MCP config; use markdown output as fallback |
| Paired mode not linking |
qa-bug-ticket-creator output not consumed |
Ensure bug ticket number is passed; use "Fixes #N" in body |
Reference Files
| Topic |
File |
| Task type templates and examples |
references/task-types.md |
| Linking patterns (bugs, requirements, coverage) |
references/linking-patterns.md |
1---2name: qa-task-creator3description: Generate work tasks from QA analysis, coverage gaps, and bug reports. Works standalone for any task creation or paired with qa-bug-ticket-creator for linked fix tasks.4---56# QA Task Creator78## Purpose910Generate structured work tasks from QA analysis outputs, coverage gaps, spec-auditor findings, risk-analyzer results, and bug reports. Supports two usage patterns: **standalone** (create tasks directly from user request) and **paired** with qa-bug-ticket-creator (auto-create linked fix/enhancement tasks from bugs).1112## Dual-Use Pattern1314| Mode | Trigger | Output |15| ---- | ------- | ------ |16| **Standalone** | User requests task creation from description, coverage gap, or spec finding | GitHub Issue (or Jira/Linear format) with full task details |17| **Paired** | Bug ticket created by qa-bug-ticket-creator | Linked fix task referencing the bug; optionally enhancement tasks for related improvements |1819When paired: bug ticket → fix task; fix task links back to bug via GitHub issue reference (e.g., "Fixes #123").2021## Input Sources2223| Source | Task Type | Example |24| ------ | --------- | ------- |25| **Coverage gaps** | Development / QA | "Add unit tests for AuthService.login() — 0% coverage" |26| **Spec-auditor findings** | Development / Documentation | "Implement validation per spec section 4.2" |27| **Risk-analyzer output** | Development / QA | "Add integration tests for payment flow — high risk" |28| **Bug reports** | Development (fix) | "Fix null pointer in checkout when cart is empty" |29| **User request** | Any | "Create task to refactor user API" |3031## Task Types3233| Type | Description | Typical Assignee |34| ---- | ----------- | ---------------- |35| **Development** | Implement, fix, refactor, optimize | Dev |36| **QA** | Write tests, increase coverage, update test data | QA |37| **Documentation** | Update specs, add diagrams, API docs | Dev/QA |38| **Enhancement** | Performance, validation, UI polish | Dev |3940See `references/task-types.md` for templates and examples.4142## Output Format4344Tasks follow GitHub Issue / Jira / Linear story format:4546- **Title** — Clear, actionable (verb + object)47- **Description** — Context, acceptance criteria, links to source48- **Labels** — `task`, `development`, `qa`, `documentation`, `enhancement`, component tags49- **Links** — Parent bug, requirement, coverage gap, or spec section50- **Acceptance criteria** — Testable conditions for done5152## Auto-Linking5354Tasks automatically link to their source:5556| Source | Link Format |57| ------ | ----------- |58| Bug | "Fixes #123" or "Related to #123" in body; GitHub auto-links |59| Requirement | Link to requirement doc or ticket |60| Coverage gap | File:line reference, module name |61| Spec section | Section reference (e.g., "Spec §4.2") |6263See `references/linking-patterns.md` for patterns.6465## Integrations6667| Integration | Use |68| ----------- | --- |69| **GitHub MCP** | Create issues, search for duplicates, link to bugs |70| **qa-bug-ticket-creator** | Consume bug ticket output; create linked fix task |71| **qa-coverage-analyzer** | Consume coverage gap output |72| **qa-spec-writer / qa-requirements-generator** | Consume spec/requirement references |7374## Trigger Phrases7576- "Create a task to [description]"77- "Generate fix task for bug #123"78- "Create tasks from coverage gaps in [path]"79- "Task from spec-auditor findings"80- "Linked fix task for [bug summary]"81- "Work items from risk analysis"82- "Development task for [feature/fix]"8384## Workflow85861. **Input** — User request, bug ticket, coverage gap, spec finding, or risk output872. **Task type** — Classify as Development / QA / Documentation / Enhancement883. **Content** — Title, description, acceptance criteria, labels894. **Links** — Add references to parent bug, requirement, or source905. **Duplicate check** — Search existing issues for similar tasks (optional)916. **Create** — Create GitHub Issue via GitHub MCP; output link9293## Scope9495**Can do (autonomous):**96- Create tasks from user description, bug tickets, coverage gaps, spec findings97- Classify task type and assign appropriate labels98- Link tasks to parent bugs, requirements, coverage gaps99- Create GitHub Issues via GitHub MCP100- Search for duplicate tasks before creating101- Work paired with qa-bug-ticket-creator for linked fix tasks102103**Cannot do (requires confirmation):**104- Assign to specific users without approval105- Set milestones or due dates without user input106- Create tasks in Jira/Linear (reference format only; adapters future)107108**Will not do (out of scope):**109- Execute development or testing work110- Modify code or configurations111- Approve or prioritize tasks (stakeholder responsibility)112113## Quality Checklist114115- [ ] Task title is actionable (verb + object)116- [ ] Description includes context and acceptance criteria117- [ ] Links to parent bug/requirement/coverage gap when applicable118- [ ] Labels match task type and component119- [ ] Acceptance criteria are testable120- [ ] No hardcoded secrets; repo/org from user or env121- [ ] Duplicate check performed when creating from coverage/spec122123## Troubleshooting124125| Symptom | Likely Cause | Fix |126| ------- | ------------ | --- |127| Task too vague | Insufficient context from source | Add explicit acceptance criteria; request clarification |128| Missing link to bug | Bug ticket not passed or not found | Verify bug exists; include bug number in description |129| Wrong task type | Misclassification of input | Use `references/task-types.md`; ask user to confirm |130| Duplicate created | Search query too narrow | Broaden search terms; check similar open issues |131| GitHub MCP fails | Token missing, repo access | Verify GitHub MCP config; use markdown output as fallback |132| Paired mode not linking | qa-bug-ticket-creator output not consumed | Ensure bug ticket number is passed; use "Fixes #N" in body |133134## Reference Files135136| Topic | File |137| ----- | ---- |138| Task type templates and examples | `references/task-types.md` |139| Linking patterns (bugs, requirements, coverage) | `references/linking-patterns.md` |
azanir