| name | specloop-loop |
| description | Run the SpecLoop QA loop: load specs and business rules, enforce read-only safety, explore critical flows, write structured findings, triage accepted reports, and suggest regression tests. |
SpecLoop Loop
Use this workflow when a user asks to run a SpecLoop QA pass, triage SpecLoop findings, or scaffold a product-specific QA loop.
Procedure
- Run
specloop doctor.
- Load cold context: product, specs, business rules, acceptance criteria, critical flows.
- Load hot context: risk register, prior findings, current run budget.
- Select a scenario from
.specloop/scenarios/ or a flow from .specloop/critical-flows.md.
- For local URLs, verify the user has started the app. Do not start unknown app servers unless asked.
- Explore one flow at a time with read-only safety.
- Save evidence under
.specloop/screenshots/ or .specloop/traces/.
- Write each finding immediately.
- Run
specloop report and specloop validate.
- Triage reviewed findings into implementation plans.
Manual Runner
After specloop scaffold scripts, these examples are available:
node --experimental-strip-types scripts/specloop-browser-smoke.ts --target local
node --experimental-strip-types scripts/specloop-browser-smoke.ts --target lemon
Rules
- Never perform destructive production actions by default.
- Do not store cookies or secrets.
- Do not batch findings until the end of a run.
- Suggest a regression test for every finding.