Jev decision module for a 14-day sprint: budget, schedule, gates
Locks a sprint to a $2,000 budget and 14-day gantt, runs six workers in dependency order, and holds every irreversible send behind an approval gate.
WHOEVER LEAKED THIS JEV DECISION MODULE DESERVES THE COO SEAT I thought running a 14-day product sprint meant a kanban board, three Slack channels, and praying nothing drifts past Wednesday. Apparently not. This module's setup is much more interesting: → BRIEF locks the whole sprint to $2,000/mo across 14 days with Opus 5.5 on delegate mode and 6 workers, no scope creep past the gantt → SCHEDULE_14D breaks the plan into named phases (D1-2 prototype, D3-7 qualify, D8-13 demo, D14 close) with cron MON 09:00, no re-planning mid-sprint → TASK TOPOLOGY wires 6 jobs in dependency order with 1 running and 4 queued, no worker starts until its upstream closes → VECTOR DB loads 1,536-dim chunks (127 so far across 48 FAQs) at $25/mo and 0.94 recall, 6 workers parallel on the dependency order → GATES hold every irreversible move (webhook pending, outreach approval needed, price waiting on you, send not approved), flags 7 drafts that tried to go out without your yes this run so you get: Briefs scoped. Schedules named. Tasks ordered. Gates held. the interesting part isn't planning harder. it's giving the whole sprint one gantt the agent can't drift past. Instead of three Slack channels and a kanban that lies by Friday, you run one playbook with --14-days --no-send, 6 workers parallel on dependency order, 2 of 4 clients modeled at $500/mo, and every send still waits on your yes. Lock the brief. Order the task. Hold the gate.
This post quotes another post: “Long read: how to build a Jev-powered agent stack”