Skip to content

afeezadebayo/email-inbox-skills / follow-up-tracking

follow-up-tracking

Verified

Track open loops in email: things others owe the user and promises the user made, captured from sent and received mail, logged with dates and thread links, checked daily, chased with short nudge templates, escalated after one nudge and reviewed weekly, with default chase intervals by relationship. Use whenever someone needs to track email replies, chase clients, suppliers or colleagues, manage promises made by email, follow up on job applications or stop things slipping through the cracks.

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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall