engine-sprints

name	engine-sprints
version	2.0
type	autoresearch
description	Self-managing sprint operations with ADD-optimized workflow
user-invocable	true
agent	ENGINE
agent_model	google/gemini-flash-1.5
mcps	["command-center","hermes","henry"]
gstack_skills	["/retro","/ship"]
eval_metric	sprint_velocity
eval_budget	30s
guard	max_active_items <= 3

/engine-sprints — Self-Managing Sprint Operations

What it does

Manages 2-week sprints with ADD/ADHD-optimized rules: max 3 active items at once, every item has owner + deadline, blockers escalated same day.

Protocol

Step 0: Load context

• memory/OPERATIONS_MEMORY.md — current sprint state
• HENRY_BRAIN.md — priorities
• command-center daily summary

Step 1: Sprint status check

Query command-center for current sprint:

TODAY items:       [list with status]
THIS WEEK items:   [list with status]
THIS SPRINT items: [list with status]
BLOCKED items:     [list with blocker]

Step 2: Enforce sprint rules

1. Max 3 active at once — if more, deprioritize or park
2. Every item has owner + deadline — if missing, assign NOW
3. Blocked items escalated same day — route to NEXUS
4. Done = shipped — not "code complete", not "in review"

Step 3: Daily standup (Hermes scheduled)

Hermes runs at 9 AM CT daily:

1. Pull current sprint from command-center
2. Check what's done, what's blocked, what's next
3. Generate standup summary
4. Flag any items past deadline

Step 4: Weekly retro (/retro)

Every Friday, run /retro:

• What shipped this week?
• What got blocked?
• What's carrying over?
• Shipping streak tracking

Step 5: Sprint planning

At sprint boundary (every 2 weeks):

1. Close out completed items
2. Move incomplete items with reason
3. Pull from backlog based on ATLAS priorities
4. Assign owners + deadlines
5. Max 10 items per sprint

Step 6: Update state

• Update command-center with all changes
• Update memory/OPERATIONS_MEMORY.md
• Set Hermes reminders for upcoming deadlines

Sprint Template

SPRINT: [date range]
GOAL: [one sentence]

TODAY (max 3):
  [ ] Item 1 — Owner: X — Due: Y
  [ ] Item 2 — Owner: X — Due: Y
  [ ] Item 3 — Owner: X — Due: Y

THIS WEEK:
  [ ] Item 4-7

THIS SPRINT:
  [ ] Item 8-10

BLOCKED:
  [ ] Item — Blocker: [description] — Escalated: [Y/N]

DONE:
  [x] Completed items with dates

Autoresearch Loop

• Metric: sprint_velocity — items completed per sprint / items planned
• Budget: 30s eval
• Modify: sprint templates, planning heuristics, standup format
• Guard: max_active_items never exceeds 3 (ADD/ADHD constraint is sacred)

MCP Integration Map

ENGINE (Gemini Flash)
  ├── command-center: task tracking, project management, daily summaries
  ├── hermes: daily standup cron, deadline reminders, blocker alerts
  ├── henry: system access for checking deployment status
  ├── /retro: weekly retrospective with shipping streaks
  └── /ship: verify "done = shipped" via deploy pipeline