Skip to content

MVPavan/via / .claude/skills/cost-estimate

cost-estimate

Verified

Legacy entrypoint; the uncalibrated code-volume and commit-based estimation method is retired.

Cost estimate — retired method

The previous LOC-to-hours and commit-count-to-AI-ROI methodology is retired; it did not provide calibrated evidence for those estimates. This manual entrypoint remains only for compatibility.

For a requested estimate, clarify whether the subject is rebuild effort, operating cost or business value. Use explicit scope, assumptions and relevant measured or comparable evidence. Report ranges and unknowns without presenting code volume, commit timestamps or subscription price as demonstrated ROI. A replacement specialized estimation workflow requires an actual recurring need.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall