How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

sddp-implement-qc-loop - Prompt

Name: sddp-implement-qc-loop
Author: evatechnosoft

Prompt file imported from evatechnosoft/sdd-pilot (.windsurf/workflows/sddp-implement-qc-loop.md). Copyright stays with the author.

You are starting an Implement + QC loop workflow. Your sole purpose is to repeatedly implement tasks and run quality control until QC passes or the safety limit is reached. Disregard any prior context from this conversation. Focus exclusively on the implement → QC cycle.

Load and follow the workflow in .github/skills/implement-qc-loop/SKILL.md.

The loop skill will instruct you to load and execute two sub-skills inline:

Implement → .github/skills/implement-tasks/SKILL.md
QC → .github/skills/quality-control/SKILL.md

When either sub-skill says Delegate, read the referenced sub-agent file at that point, not before — then perform the task yourself:

Delegate: Context Gatherer → .github/agents/_context-gatherer.md
Delegate: Task Tracker → .github/agents/_task-tracker.md
Delegate: Developer → .github/agents/_developer.md
Delegate: Checklist Reader → .github/agents/_checklist-reader.md (only during gates.md checklist gate)
Delegate: Test Evaluator → .github/agents/_test-evaluator.md (only during gates.md checklist gate, when checklists FAIL)
Delegate: Technical Researcher → .github/agents/_technical-researcher.md
Delegate: QC Auditor → .github/agents/_qc-auditor.md
Delegate: Story Verifier → .github/agents/_story-verifier.md

Report progress to the user at each iteration boundary — summarize what was fixed and what remains.

Install sddp-implement-qc-loop and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "You are starting an Implement + QC loop workflow. Your sole purpose is to repeatedly implement tasks and run quality control until QC passes or the safety limit is reached. Disregard any prior context from this conversation. Focus exclusively on the implement → QC cycle.\n\nLoad and follow the workflow in `.github/skills/implement-qc-loop/SKILL.md`.\n\nThe loop skill will instruct you to load and execute two sub-skills inline:\n- **Implement** → `.github/skills/implement-tasks/SKILL.md`\n- **QC** → `.github/skills/quality-control/SKILL.md`\n\nWhen either sub-skill says **Delegate**, read the referenced sub-agent file **at that point, not before** — then perform the task yourself:\n- **Delegate: Context Gatherer** → `.github/agents/_context-gatherer.md`\n- **Delegate: Task Tracker** → `.github/agents/_task-tracker.md`\n- **Delegate: Developer** → `.github/agents/_developer.md`\n- **Delegate: Checklist Reader** → `.github/agents/_checklist-reader.md` *(only during gates.md checklist gate)*\n- **Delegate: Test Evaluator** → `.github/agents/_test-evaluator.md` *(only during gates.md checklist gate, when checklists FAIL)*\n- **Delegate: Technical Researcher** → `.github/agents/_technical-researcher.md`\n- **Delegate: QC Auditor** → `.github/agents/_qc-auditor.md`\n- **Delegate: Story Verifier** → `.github/agents/_story-verifier.md`\n\nReport progress to the user at each iteration boundary — summarize what was fixed and what remains.", "variables": [], "notes": "You are starting an Implement + QC loop workflow. Your sole purpose is to repeatedly implement tasks and run quality control until QC passes or the safety limit is reached. Disregard any prior context from this conversation. Focus exclusively on the implement → QC cycle.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/evatechnosoft/sdd-pilot", "path": ".windsurf/workflows/sddp-implement-qc-loop.md", "ref": "e04c29639cec60b77d60f60a206e8479feee2413", "url": "https://github.com/evatechnosoft/sdd-pilot/blob/e04c29639cec60b77d60f60a206e8479feee2413/.windsurf/workflows/sddp-implement-qc-loop.md", "key": "evatechnosoft/sdd-pilot/.windsurf/workflows/sddp-implement-qc-loop.md" } } }

sddp-implement-qc-loop

About

Use it

Install sddp-implement-qc-loop and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews