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.

verify-implementation-against-summary - Prompt

Name: verify-implementation-against-summary
Author: TekupDK

Prompt file imported from TekupDK/friday-ai (.cursor/commands/development/verify-implementation-against-summary.md). Copyright stays with the author.

Verify Implementation Against Summary

You are verifying that an implementation matches what was discussed in a chat summary.

TASK

Compare implemented code against the chat summary to ensure everything was done correctly and precisely.

COMMUNICATION STYLE

Tone: Verification-focused, precise, thorough
Audience: Developers and QA
Style: Detailed verification with specific findings
Format: Markdown with verification report

REFERENCE MATERIALS

Chat summary - Requirements and decisions
Implemented code - What was built
docs/DEVELOPMENT_GUIDE.md - Development patterns
docs/ARCHITECTURE.md - Architecture

TOOL USAGE

Use these tools:

Review chat summary - Understand requirements
read_file - Read implemented code
codebase_search - Find related code
grep - Search for patterns
run_terminal_cmd - Run tests

DO NOT:

Skip verification
Miss requirements
Ignore constraints
Overlook deviations

REASONING PROCESS

Before verifying, think through:

Understand requirements:
- What was requested?
- What were constraints?
- What were decisions?
Review implementation:
- What was built?
- What files changed?
- What patterns used?
Compare:
- Requirements vs implementation
- Constraints respected?
- Decisions followed?
Identify gaps:
- What's missing?
- What's different?
- What needs fixing?

STEPS

Read the chat summary:
- Understand all requirements
- Note constraints and "don't do" items
- Identify technical decisions
- Review acceptance criteria
Review the implementation:
- Check all files modified
- Review code changes
- Verify patterns used
- Check test coverage
Check requirements coverage:
- Verify each requirement is implemented
- Check acceptance criteria met
- Ensure nothing was missed
- Verify nothing extra was added (if not discussed)
Verify constraints:
- Check "don't do" items were avoided
- Verify constraints respected
- Ensure no shortcuts taken
Verify technical decisions:
- Check discussed patterns were used
- Verify architecture decisions followed
- Ensure technology choices respected
Identify gaps:
- Missing requirements
- Incomplete implementations
- Deviations from summary
- Areas needing clarification
Provide feedback:
- What matches perfectly
- What needs adjustment
- What's missing
- What should be removed (if added)

OUTPUT

Provide:

Verification summary
Requirements coverage (✓/✗)
Constraints verified
Technical decisions checked
Gaps identified
Recommendations for fixes

Install verify-implementation-against-summary 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.

# Verify Implementation Against Summary You are verifying that an implementation matches what was discussed in a chat summary. ## TASK Compare implemented code against the chat summary to ensure everything was done correctly and precisely. ## COMMUNICATION STYLE - **Tone:** Verification-focused, precise, thorough - **Audience:** Developers and QA - **Style:** Detailed verification with specific findings - **Format:** Markdown with verification report ## REFERENCE MATERIALS - Chat summary - Requirements and decisions - Implemented code - What was built - `docs/DEVELOPMENT_GUIDE.md` - Development patterns - `docs/ARCHITECTURE.md` - Architecture ## TOOL USAGE **Use these tools:** - Review chat summary - Understand requirements - `read_file` - Read implemented code - `codebase_search` - Find related code - `grep` - Search for patterns - `run_terminal_cmd` - Run tests **DO NOT:** - Skip verification - Miss requirements - Ignore constraints - Overlook deviations ## REASONING PROCESS Before verifying, think through: 1. **Understand requirements:** - What was requested? - What were constraints? - What were decisions? 2. **Review implementation:** - What was built? - What files changed? - What patterns used? 3. **Compare:** - Requirements vs implementation - Constraints respected? - Decisions followed? 4. **Identify gaps:** - What's missing? - What's different? - What needs fixing? ## STEPS 1) Read the chat summary: - Understand all requirements - Note constraints and "don't do" items - Identify technical decisions - Review acceptance criteria 2) Review the implementation: - Check all files modified - Review code changes - Verify patterns used - Check test coverage 3) Check requirements coverage: - Verify each requirement is implemented - Check acceptance criteria met - Ensure nothing was missed - Verify nothing extra was added (if not discussed) 4) Verify constraints: - Check "don't do" items were avoided - Verify constraints respected - Ensure no shortcuts taken 5) Verify technical decisions: - Check discussed patterns were used - Verify architecture decisions followed - Ensure technology choices respected 6) Identify gaps: - Missing requirements - Incomplete implementations - Deviations from summary - Areas needing clarification 7) Provide feedback: - What matches perfectly - What needs adjustment - What's missing - What should be removed (if added) ## OUTPUT Provide: - Verification summary - Requirements coverage (✓/✗) - Constraints verified - Technical decisions checked - Gaps identified - Recommendations for fixes

{ "prompt": "# Verify Implementation Against Summary\n\nYou are verifying that an implementation matches what was discussed in a chat summary.\n\n## TASK\n\nCompare implemented code against the chat summary to ensure everything was done correctly and precisely.\n\n## COMMUNICATION STYLE\n\n- **Tone:** Verification-focused, precise, thorough\n- **Audience:** Developers and QA\n- **Style:** Detailed verification with specific findings\n- **Format:** Markdown with verification report\n\n## REFERENCE MATERIALS\n\n- Chat summary - Requirements and decisions\n- Implemented code - What was built\n- `docs/DEVELOPMENT_GUIDE.md` - Development patterns\n- `docs/ARCHITECTURE.md` - Architecture\n\n## TOOL USAGE\n\n**Use these tools:**\n- Review chat summary - Understand requirements\n- `read_file` - Read implemented code\n- `codebase_search` - Find related code\n- `grep` - Search for patterns\n- `run_terminal_cmd` - Run tests\n\n**DO NOT:**\n- Skip verification\n- Miss requirements\n- Ignore constraints\n- Overlook deviations\n\n## REASONING PROCESS\n\nBefore verifying, think through:\n\n1. **Understand requirements:**\n - What was requested?\n - What were constraints?\n - What were decisions?\n\n2. **Review implementation:**\n - What was built?\n - What files changed?\n - What patterns used?\n\n3. **Compare:**\n - Requirements vs implementation\n - Constraints respected?\n - Decisions followed?\n\n4. **Identify gaps:**\n - What's missing?\n - What's different?\n - What needs fixing?\n\n## STEPS\n\n1) Read the chat summary:\n - Understand all requirements\n - Note constraints and \"don't do\" items\n - Identify technical decisions\n - Review acceptance criteria\n\n2) Review the implementation:\n - Check all files modified\n - Review code changes\n - Verify patterns used\n - Check test coverage\n\n3) Check requirements coverage:\n - Verify each requirement is implemented\n - Check acceptance criteria met\n - Ensure nothing was missed\n - Verify nothing extra was added (if not discussed)\n\n4) Verify constraints:\n - Check \"don't do\" items were avoided\n - Verify constraints respected\n - Ensure no shortcuts taken\n\n5) Verify technical decisions:\n - Check discussed patterns were used\n - Verify architecture decisions followed\n - Ensure technology choices respected\n\n6) Identify gaps:\n - Missing requirements\n - Incomplete implementations\n - Deviations from summary\n - Areas needing clarification\n\n7) Provide feedback:\n - What matches perfectly\n - What needs adjustment\n - What's missing\n - What should be removed (if added)\n\n## OUTPUT\n\nProvide:\n- Verification summary\n- Requirements coverage (✓/✗)\n- Constraints verified\n- Technical decisions checked\n- Gaps identified\n- Recommendations for fixes", "variables": [], "notes": "You are verifying that an implementation matches what was discussed in a chat summary.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/TekupDK/friday-ai", "path": ".cursor/commands/development/verify-implementation-against-summary.md", "ref": "7b500f2f374b918d03a28f2450f1f8a8b95c8847", "url": "https://github.com/TekupDK/friday-ai/blob/7b500f2f374b918d03a28f2450f1f8a8b95c8847/.cursor/commands/development/verify-implementation-against-summary.md", "key": "TekupDK/friday-ai/.cursor/commands/development/verify-implementation-against-summary.md" } } }

verify-implementation-against-summary

About

Verify Implementation Against Summary

TASK

COMMUNICATION STYLE

REFERENCE MATERIALS

TOOL USAGE

REASONING PROCESS

STEPS

OUTPUT

Install verify-implementation-against-summary 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

Use it

Manifest

Reviews