Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-09-09 09:15:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(ai-team-orchestration): add role guidance, PR checklist, QA risk matrix, and sample prompts (#2946)

Browse Source 
Improve the ai-team-orchestration skill references:
- anti-patterns.md: Do/Don't role responsibilities (Producer/Dev/QA) and decision-log guidance
- brainstorm-format.md: minimal sample prompts for Producer, Dev, and QA agents
- sprint-plan-template.md: concrete acceptance-criteria examples, PR checklist, and a QA risk matrix
- project-brief-template.md: onboarding checklist and where to record decisions

Co-authored-by: sinamorida <sinamorida@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Aaron Powell <me@aaron-powell.com>
This commit is contained in:
sina morida
2026-09-07 12:45:16 +10:00
committed by GitHub
co-authored by sinamorida Copilot App Aaron Powell
parent 877b3f0640
commit 87ba8b1780
4 changed files with 69 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/ai-team-orchestration/references/anti-patterns.md
+19
View File
@@ -11,3 +11,22 @@
| Bugs and decisions kept only in chat | Use the repository's issue tracker and durable context | Future sessions can discover them. |
| QA fixes application source | QA reports behavior; Dev implements fixes | Separation preserves independent verification. |
| Treating every automated suggestion as a requirement | Assess relevance, confidence, scope, and practical risk | Review should improve the product, not expand scope without limit. |
## Role responsibilities (Do / Don't)
- Producer
- Do: Clarify outcome, constraints, acceptance criteria, and explicit exclusions; coordinate reviewers and merge policy.
- Don't: Implement or ship code changes that should be reviewed by Dev.
- Dev
- Do: Implement the smallest complete solution, run listed verification, include tests, and prepare the PR with verification steps.
- Don't: Merge without required checks, failing tests, or without documenting risks and decisions.
- QA (optional)
- Do: Independently verify behavior, file reproducible issues, and confirm fixes after Dev applies them.
- Don't: Modify application source as a shortcut for failing verification — report and hand back to Dev.
## Decision logging guidance
- Record material decisions in a DECISIONS.md or the repository issue tracker with: title, date, owner, decision summary (1 line), rationale, and link to related PR/issue.
- Keep entries short and searchable; record the next action when a decision defers work.