Ultrapower

⚡ Ultrapower

A Claude Code plugin that fuses Scrum (lightweight management) with Extreme Programming (quality engineering) into one enforced workflow: plan a sprint, drive each story test-first with codegraph grounding, get a navigator review, and pass a verify-gate before anything closes — all under an always-on lean ladder (YAGNI → stdlib → native → one line) that keeps every change minimal.

Commands are namespaced /up: (the plugin is named up).

The loop

/up:init               once per project — detect verify commands + Definition of Done
/up:lean [level]       dial the always-on lean ladder (lite|full|ultra|off; default full)
/up:sprint plan        guided question-bundle → crisp sprint goal + estimated backlog
/up:story start <id>   brief + codegraph impact/reuse → you approve → debate pre-lock plan review → file contract locked
  (implement)          TDD: failing test → mark-red → minimal code → refactor
/up:done               navigator + done-gate → auto-mark done, release lock, queue for tutoring
/up:sprint close       record velocity → /up:retro
/up:tutor [target]     understand the code to mastery — or drain the pending queue → tutored.md

How to use — a worked example

New to it? Here's a full pass for a small task: "reject malformed emails on the signup form."

0. One-time setup (per project)

/up:init

It scans the repo, proposes the commands it found (e.g. pytest -q, ruff check ., mypy, and a run/boot smoke), and asks you to confirm. Writes .scrum/config.json.

1. Plan the sprint

/up:sprint plan

It interviews you with a few quick questions (what's the goal? what's in/out of scope? how big?), then proposes a sprint goal and a short backlog with point estimates — e.g. "S1 — reject malformed emails on signup (2 pts)". You tweak and approve; it writes .scrum/sprint.md.

2. Start a story

/up:story start S1

The story-planner reads the codebase via codegraph and hands you a brief: which files it'll touch, the approach, which existing helpers it reuses, the tests, and a verify command. You approve → the debate agent runs a pre-lock plan review (six lenses, VERDICT: proceed | revise-plan) → that file list is locked (edits outside it get blocked).

3. Build it test-first

• Write the failing test first — test_rejects_malformed_email → run it → it fails (red). Required.
• Now source edits unlock — write the minimal validator to make it pass (green).
• Refactor with the test staying green.

If you try to edit the validator before a failing test exists, the tdd-guard stops you — that's the plugin keeping you honest, not a bug. (No active story? All guards are off.)

4. Finish the story

/up:done

The navigator reviews your diff against the brief (missing test? a caller you forgot? scope creep?) and lists findings. Fix any blockers, then the done-gate runs your verify set (tests + lint + typecheck + smoke). Green + no blockers → the story is auto-marked done, the lock releases, the increment is tagged, and the story is queued for tutoring — work the queue anytime with /up:tutor. No hand-editing of .scrum/ state.

5. Repeat & wrap up

/up:sprint close     # records velocity for next sprint's planning
/up:retro            # quick 3-bullet retrospective

Reach for these as needed:

• /up:refactor <target> — restructure with no behavior change (checks every caller via codegraph first, keeps tests green).
• /up:story add "<idea>" — capture a backlog idea without planning it yet.
• /up:tutor [target] — a tutor drills you to mastery over a story's diff, a file/area, the whole project, or a topic; with no target it drains the pending queue. Saves deduped notes to tutored.md.

Commands

Command	What it does
/up:init	Detect & confirm this project's test/lint/typecheck/smoke commands and Definition of Done → .scrum/config.json.
/up:lean [lite|full|ultra|off]	Dial the always-on lean ladder's intensity (default full); persists as lean_mode.
/up:sprint plan | close	Plan a sprint via a guided question-bundle; close records velocity and seeds the retro.
/up:story start <id|desc> | add	Plan + lock a story (brief, estimate, contract); or quick-add one to the backlog.
/up:done	Navigator review + done-gate, then close the active story.
/up:refactor <target>	Codegraph-impact-checked refactor with tests green throughout.
/up:retro	Short retrospective appended to .scrum/retro.md.
/up:tutor <target>	Tutor-driven deep-understanding session over a story, a file/area, the whole project, or a topic; saves what you learn to tutored.md.

Agents