← ClaudeAtlas

ship-day-plannerlisted

Turn the operator's one-line product hypothesis into the 8 ship-day blocks from `workflows/ship-a-product-in-a-day.md` — night-before frame, domain + repo, skeleton, forms + analytics, deploy, SEO baseline, first content piece, post-day update — each timeboxed with the specific commands or skills to invoke.
mccarthy606/claude-operator-stack · ★ 0 · AI & Automation · score 61
Install: claude install-skill mccarthy606/claude-operator-stack
# Ship Day Planner The 8-block ship-day in `workflows/ship-a-product-in-a-day.md` is the most-quoted workflow in the repo: from a one-line idea to a live URL with lead capture, real analytics, and a first content piece, in a single focused day. This skill takes a hypothesis sentence and produces the structured day-plan — every block timeboxed, every block named with the tool or skill that owns it, every block with a "done when" criterion. The plan is what the operator opens at 8:00 AM; the workflow is what the plan executes against. ## When to Use - The operator says "let's plan a ship day", "split this into the 8 blocks", "I want to ship <X> tomorrow", or any variant. - The operator opens a fresh Claude Code session in a new product directory and asks for the day's structure before doing any of the work. - The operator returns from a stalled prototype and needs to re-enter the ship-day loop with a tightened scope. - The operator is teaching another founder the workflow and wants a concrete worked example for their idea. - ECC has `blueprint` (architecture decisions) and `team-builder` (multi-agent setup). Neither targets the one-day-to-live-URL cadence with the 8 specific blocks; use this one for the ship-day plan. ## Inputs - The hypothesis sentence. One line answering "what do I believe about this market that I want to test?" — the night-before frame from block 0 of the workflow. If the operator has not provided one, prompt for it before producing any blocks. - The as