no-deferred-work

Enforces complete implementations by banning TODO comments and placeholder code during development.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill no-deferred-work-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: no-deferred-work
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/no-deferred-work
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill no-deferred-work-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deferred work in the form of TODO comments, FIXME markers, and placeholder implementations accumulates as technical debt and is frequently forgotten, leading to incomplete features and production issues. ## Core Features & Use Cases - Forbidden Pattern Detection: Identifies TODO, FIXME, HACK, and XXX comments plus placeholder implementations that should never be committed. - Decision Flow for Scope: Provides a structured flowchart to decide whether discovered work belongs in the current change or a separate tracked issue. - Exception Process: Defines how to request explicit deferral permission and create properly tracked issues with acceptance criteria instead of inline TODOs. - Use Case: While implementing a user registration feature, you discover email verification is needed. Instead of leaving a TODO, you either implement it fully or create a tracked issue with acceptance criteria and reference it in code. ## Quick Start Review my current changes and flag any TODO comments, placeholder implementations, or incomplete error handling before I commit.

Frequently Asked Questions about no-deferred-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle work that is out of scope without leaving a TODO?▼

Create a tracked issue with a full description, acceptance criteria, and a link to where the work was discovered, then reference that issue number in the code. This replaces informal TODO comments with accountable, trackable work items.

What should I do instead of writing a TODO comment in code?▼

Either implement the work immediately if it is in scope, or create a separate issue and reference it in a comment if explicitly approved as out of scope. A reference to a tracked issue is not a TODO.

How can I automatically block TODO comments before committing?▼

Add a pre-commit hook that greps the staged diff for TODO, FIXME, HACK, or XXX markers and exits with an error if found. This forces the author to complete the work or file an issue before committing.

When is it acceptable to defer work during development?▼

Deferral is acceptable only after getting explicit permission from your human partner, creating a properly tracked issue with acceptance criteria, and referencing that issue in the code. Time pressure or low perceived importance are not valid reasons.

Why are placeholder implementations considered harmful?▼

Placeholder implementations like returning empty objects or swallowing errors hide incomplete work that often ships to production. They create silent failures and technical debt that is rarely revisited once committed.