add-new-provider
Add a new AI provider "$ARGUMENTS" to the OpenUsage TUI dashboard.
Implement the feature "$ARGUMENTS" from its design doc.
How it fires
How this command gets triggered: by you, by Claude, or both.
/implement-featureContext preview
What this command does when you run it.
Implement the feature "$ARGUMENTS" from its design doc.
Implement the feature "$ARGUMENTS" from its design doc.
Read and follow the full skill specification in docs/skills/implement-feature/SKILL.md.
Follow all phases in order:
1. **Phase 0 — Load**: Read the design doc, extract tasks and scope. 2. **Phase 1 — Codebase Analysis**: Read affected files, note patterns. 3. **Phase 1.5 — Pre-Implementation Quiz**: Surface ambiguities. 4. **Phase 2 — Execution Plan**: Present tasks with approaches and risks. 5. **Phase 3 — Implement**: Execute tasks in dependency order with tests. 6. **Phase 4 — Integration Check**: Build, test, verify. 7. **Phase 5 — Summary**: Report changes and status.
The one dashboard you’ve been looking for — track spend and usage across Claude, Cursor, OpenRouter, Copilot, Gemini, Codex, and more.
Add a new AI provider "$ARGUMENTS" to the OpenUsage TUI dashboard.
Design a new feature "$ARGUMENTS" for the OpenUsage TUI dashboard.
Audit and improve the development workflow for OpenUsage.
Develop the feature "$ARGUMENTS" end-to-end — from design to pull request.
Finalize the feature "$ARGUMENTS" — create branch, commit, and open PR.