cowork-tax-prep-organizer
Sweep your folders and downloads for tax documents and build a CPA-ready package -- checklist by form type, everything renamed and organized, a missing-document chase list, and flagged items worth asking your accountant about. Organization, not tax advice.
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/cowork-tax-prep-organizer && cp -r /tmp/cowork-tax-prep-organizer/cowork-tax-prep-organizer ~/.claude/skills/cowork-tax-prep-organizerSKILL.md
# Cowork Tax Prep Organizer
Do the part of tax season that actually eats the weekend: finding, identifying, and organizing the documents. Input: one or more folders (Downloads, a documents dump, last year's tax folder for reference). Output: an organized package a CPA can work from and a precise list of what is still missing. This skill organizes; it does not compute taxes or give tax advice.
## Workflow
1. **Build the personal checklist.** From last year's return or folder (if provided) and a few questions (W-2 employment? contract income? brokerage accounts? mortgage? dependents? business entity?), build the expected-documents list: W-2s, 1099-NEC/MISC/INT/DIV/B/R, 1098s, K-1s, property tax bills, charitable receipts, estimated-payment confirmations, prior-year return.
2. **Sweep.** Walk the folders and identify every tax-relevant document by content, not just filename -- payers, form types, tax year. Match each to the checklist. Flag wrong-year documents (the 2024 1099 hiding in the 2025 pile) and duplicates (the same W-2 downloaded three times).
3. **Organize.** On approval, copy -- never move -- into a clean structure: `tax-2025/income/`, `deductions/`, `investments/`, `business/`, `prior-year/`, with names like `1099-nec-acme-corp-2025.pdf`. Write `INDEX.md` mapping checklist to files.
4. **Chase list.** Output what is expected but missing, with where it likely lives ("Interest income appeared last year from Chase -- no 1099-INT found; check the bank's tax documents page, typically posted by Jan 31"). Sort by what blocks filing vs. nice-to-have.
5. **Ask-your-CPA list.** Flag items a preparer should look at -- not conclusions: home-office-looking expenses for the self-employed, a brokerage form showing wash-sale codes, K-1 arrived vs. expected, estimated payments that do not sum to the notes. Phrase each as a question for the professional.
## Rules
- Never compute tax liability, deductions, or refunds. Identify, organize, and question -- the CPA concludes.
- Copy, never move. Source folders stay intact.
- Tax year discipline: every document is tagged with its year, and wrong-year files are quarantined in the report, not the package.
- "MISSING" means "not found in the provided folders" -- state what was searched.
- Treat everything as sensitive: no SSNs, account numbers, or dollar amounts in console output or digests; specifics live only in the package files.
- If both spouses' or multiple entities' documents are mixed, separate them explicitly and confirm the split before organizing.
## Scheduled Mode
As a monthly Cowork scheduled task during January-April: re-sweep Downloads and the documents folder for newly arrived forms, file them into the package, and update the chase list -- so tax weekend becomes tax hour.
## Quick Commands
- "Organize my tax docs from [folder]" -- full workflow
- "What am I missing?" -- steps 1, 2, 4
- "Build my checklist" -- step 1 only
- "Anything my CPA should see?" -- step 5 against the organized packageAudit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.
Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.
Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.
Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.