← ClaudeAtlas

plan-write-reviewlisted

Produces long outputs by having the main model plan and classify, cheap subagents (Haiku) draft routine sections in parallel, the main model write the hard core itself, then skim and cross-check the routine drafts before merging and publishing. Use when the user asks for a long report, article, documentation, or multi-section write-up that splits into independent parts, or says to save tokens. Skip for short outputs.
Vumb-VibeCoder/haiku-delegate · ★ 1 · AI & Automation · score 74
Install: claude install-skill Vumb-VibeCoder/haiku-delegate
# Plan, write, review The stronger model plans, writes the core, and checks. Haiku drafts the routine parts. You MUST follow the flow and checklist below in order. Do not treat this skill as background reading. ## Flow ``` [Plan and classify] (stronger model) | +-----------+-----------+ v v [ROUTINE chunks] [CORE chunks] | | Haiku drafts raw You write them (parallel, 1 msg) directly (while Haiku runs) | | Skim + cross-check | (fix or resend once) | | | +-----------+-----------+ v [Merge and publish] ``` ## Checklist Copy this into your reply and tick items as you go: ``` - [ ] 1. Gate: long or multi-section (about 800+ words or 3+ independent sections)? If not, write directly and stop. - [ ] 2. Plan: goal, audience, tone, format, length, outline. - [ ] 3. Classify each chunk ROUTINE or CORE (apply the cost check: small chunks are CORE). - [ ] 4. Fact sheet: number every hard fact (F1, F2, ...) with its source. - [ ] 5. Fork: spawn one Haiku per ROUTINE chunk in a single message; meanwhile write all CORE chunks yourself. - [ ] 6. Skim each routine draft (tone, coverage, repetition, forbidden specifics). - [ ] 7. Cross-check each routine draft's CLAIMS list against the fact sheet. - [ ] 8. Fix inline, or resend a section to Haiku once; if it fails again, r