cskwork/supergoal-skill / skills/supergoal
supergoal
UnverifiedRoute objective-driven development, verification, planning, "teach/explain", codebase learning, and skill evaluation through the Supergoal workflow. Use when Supergoal is requested or an autonomous delivery workflow is needed.
templates/qa-report.md
View on GitHub<!--
QA-ONLY human report. Fill from the qa-auditor summary. Keep it readable by a non-engineer.
Prose in the docs language (SKILL.md). Keep the `##` anchor headings in English (the gate greps them)
and file paths/commands verbatim.
No credentials, no raw DB rows, no PII.
-->
# QA report - <objective>
- Date: <YYYY-MM-DD> Target: <url/env> Driver: <agent-browser | playwright-cli fallback | CLI smoke>
- Comparison: <functional | data-integrity | before-after | ab | env>
- Verdict: <PASS | FAIL | PARTIAL> Actions used: <action_count>/<action_cap>
## Impact coverage
<what the Impact Matrix covered: selected feature-specific scenario family, direct feature path,
before/during/after actions, adjacent screens/APIs, displayed data consistency/state propagation paths,
roles, data checks, viewport/device checks, failure/retry paths. Keep it short but specific.>
- Covered: <must scenario group> -> <evidence path>
- Covered: <adjacent/shared-state or displayed-data propagation group> -> <evidence path>
## What worked
<plain-language list of scenarios/checks that passed, each with its evidence path>
- <scenario> -> PASS (`qa/to-be-<view>.png`)
## What didn't
<scenarios/checks that failed, each with observed vs expected and evidence. Each failure must have a
matching item under `## Reproduction notes`.>
- <scenario> -> FAIL: expected <x>, saw <y> (`qa/as-is-<view>.png`)
## What I discovered
<concrete findings worth the user's attention: a UI value that disagreed with the DB source of truth,
a broken edge case, an A/B / before-after difference, a data-integrity gap. One finding per bullet.>
- <finding> (evidence: `qa/<file>`)
## Reproduction notes
<for each issue, make it easy for a human to reproduce without reading the transcript. If there are no
issues, write "No issues to reproduce.">
- <issue id/title>
Reproduce:
1. Target: <url/env>; role/account type: <role only, no credentials>.
2. Starting state: <data/settings/navigation state>.
3. Steps: <click/type/navigate sequence>.
4. Expected: <expected result>.
5. Actual: <actual result>.
Evidence: `qa/<file>`
## Not covered
<scenario groups from the Impact Matrix that were not exercised, plus why and the residual risk. Use
"None" only if every planned must/should scenario was covered within the action cap.>
- <scenario group> -> not covered because <blocker>; risk: <what could still regress>
- DB evidence: Not covered -> reason: <missing/skipped/unsafe access>; risk: <what data mismatch could still hide>
## How to re-run
<the exact way to reproduce this check next time, so it is repeatable>
- Suite: `.domain-agent/qa/<suite>.md`
- Command / spec: `<re-run command or qa/<suite>/<flow>.spec.ts>`
- DB checks: <named checks; read-only; connection from <env|config path>>
<!-- If the action cap was hit: list what remains so a follow-up run can continue. -->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |