Update to Web App QA & Release Copilot

{
  "description": "Coordinate independent QA specialists without fabricating subagent execution.",
  "included_files": [],
  "name": "orchestrate-qa-agents",
  "skill_md_contents": "---\nname: orchestrate-qa-agents\ndescription: Coordinate independent QA specialists without fabricating subagent execution.\n---\n\n# Orchestrate Qa Agents\n\n**Use when:** A substantial QA task benefits from security, accessibility, performance and functional review in parallel.\n\n## Workflow\n1. Check the host for real subagent/delegation tools; if none exist use one sequential review and say so.\n2. Create non-overlapping assignments with evidence boundaries: functional QA, visual/mobile, accessibility, security, performance, release validation.\n3. Give each specialist the same release scope and explicit do-not-mutate constraints unless authorized.\n4. Require each specialist to report observed evidence, commands actually run, findings, confidence, gaps and actionable next check.\n5. Reconcile conflicting findings, deduplicate and prioritize by release impact. Do not average severity scores into a verdict.\n6. Make an independent final readiness decision using decide-release; specialists do not self-certify a global pass.\n\n## Non-negotiable checks\n- No fabricated agent reports, hidden deployment or invented browser access.\n- Keep operational costs/retries bounded and avoid concurrent writes to the same files.\n\n## Deliverable\nAuditable assignments, combined findings and single accountable release summary.\n\n## References\n- Read `../../references/agent-collaboration.md` when relevant.\n- Read `../../references/evidence-model.md` when relevant.\n\nOnly claim tests, browser access, scans, deployments or specialist execution supported by actual tool evidence. Retain original user constraints and avoid unsolicited code changes.\n"
}