Activate when: user says 'everyone is working hard but results are flat', 'where is our bottleneck', 'we keep adding capacity but throughput doesn't improve'...
Coding
Tax Prep — Season Throughput (Theory of Constraints)
Try itActivate when: returns are piling up before a deadline; reviewer/preparer is the bottleneck; 'we can't get through them all,' 'clients waiting on missing doc...
What it does
Activate when: returns are piling up before a deadline; reviewer/preparer is the bottleneck; 'we can't get through them all,' 'clients waiting on missing docs,' planning staffing for Jan–Apr. Do NOT activate when: off-season, low volume; the issue is a single stuck return (use debugging, not capacity theory). More: deciqai.com/c/tax-season-throughput-constraints
The skill document
Tax Prep — Season Throughput (Theory of Constraints)
Industry front door for theory-of-constraints. Adds domain triggers, example, packs only. Parent Process unchanged.
Activate when: returns are piling up before a deadline; reviewer/preparer is the bottleneck; "we can't get through them all," "clients waiting on missing docs," planning staffing for Jan–Apr. Do NOT activate when: off-season, low volume; the issue is a single stuck return (use debugging, not capacity theory).
Why this variant
The parent theory-of-constraints finds the one step that caps total output and subordinates everything to it. In a tax practice the constraint is almost never "preparation" — it's usually the reviewer or client missing-documents. Optimizing anything else is wasted motion during season.
Domain inputs → parent's Process
Pipeline stages: intake → doc-complete → prep → review → e-file.
- Measure WIP at each stage; the stage with the growing queue = constraint.
- Exploit: protect reviewer time (no admin), pre-triage returns so review is fast.
- Subordinate: preparers pace to reviewer capacity, not their own.
- Elevate: add reviewer capacity / async review / raise complexity threshold for partner review.
Worked example
80 returns in "prep-done," 6 cl2ear/day through review → 13-day backlog vs 5 days to deadline. → Constraint = review. Exploit: batch simple returns for a fast lane; move partner off prep entirely. Missing-docs is the upstream feeder — a chaser (see onboarding/data-room agents) protects the constraint from starving.
Packs
- Solo: one fast-lane vs deep-lane split; cap daily complex intake.
- Firm: reviewer-protected calendar; WIP board; extension-triage rule when backlog > days-remaining.
Red flags
- Preparers "busy" but review queue growing = optimizing the non-constraint.
- Missing-docs starving the constraint (idle reviewer waiting on clients).
Verification
- Constraint stage identified by queue growth, not opinion
- Non-constraint work subordinated to it
- Extension policy triggered when backlog > remaining days
- Upstream doc-chaser keeps constraint fed
Part of deciqAI Knowledge Skills. Core method: theory-of-constraints.
Part of deciqAI Knowledge Skills — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/tax-season-throughput-constraints · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.
Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/tax-season-throughput-constraints.json
Related skills
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Activate when: a return has aggressive/uncertain positions (large Schedule C losses, high meals/vehicle, hobby-vs-business, real-estate professional status,...
Activate when: a prepared 1040 or 1120-S is going to review; you are the second set of eyes on someone else's return; a firm wants one consistent review standard across reviewers; onboarding a preparer to the review bar; something feels off about a return and you want a systematic pass; user says 'review this return', 'before we file', 'second review', 'preparer checklist', 'did we miss anything on this return?'. Do NOT activate when: the return is not yet prepared; the question is a single technical treatment; the work is chasing missing documents rather than reviewing; the question is what an examiner would attack or whether a position invites audit rather than whether the return is right (use tax-prep-pre-file-audit-premortem instead — it applies to 1120-S as much as 1040). More: deciqai.com/c/cpa-return-review
Activate when: a position/election has effects beyond this year — S-corp election, depreciation/§179/bonus, accounting-method change, filing status, Roth con...
Activate when: self-employed / K-1 / variable-income client planning quarterly 1040-ES; 'how much should I set aside?', 'will I owe a penalty?', volatile inc...