feat: add ultrapower mode with superpowers workflow integration

[yulianggan]

Summary

• Add ultrapower keyword detection (triggers: ulo, ultrapower)
• Implement getUltrapowerMessage with planner/executor mode differentiation
• Add toast notification for ultrapower mode activation

Ultrapower Mode Workflow

Planner Mode (Prometheus, Planner agents)

1. Invoke brainstorming skill
2. Ask user about using-git-worktrees skill
3. Invoke writing-plans skill
4. Save plan to docs/plans/YYYY-MM-DD-<feature>.md
5. Prompt user to run /start-work for execution

Executor Mode (Sisyphus, other agents)

1. Invoke brainstorming skill
2. Ask user about using-git-worktrees skill
3. Invoke writing-plans skill
4. Auto-execute subagent-driven-development skill
5. Invoke finishing-a-development-branch skill

Changes

• detector.ts: Add ultrapower to DetectedKeyword type
• constants.ts: Add getUltrapowerMessage() function and ultrapower detector
• index.ts: Add ultrapower toast notification and session filtering
• index.test.ts: Add comprehensive ultrapower tests (12 new tests)

Testing

All 27 tests pass:

bun test src/hooks/keyword-detector/index.test.ts
27 pass, 0 fail

---

Summary by cubic

Adds Ultrapower mode triggered by “ulo” or “ultrapower,” embedding the superpowers workflow with planner vs executor behavior, stricter phase enforcement, and a toast for activation. Also updates session filtering so Ultrapower (and Ultrawork) can run in subagent sessions.

• New Features

  • Detect “ultrapower”/“ulo” and inject mode instructions; treat these as trigger commands and ignore them in the user's request.
  • Planner: brainstorming → optional git worktree → writing-plans → save plan → prompt /start-work. Executor: brainstorming → optional git worktree → writing-plans → subagent-driven-development → finishing-a-development-branch.
  • Require first response to say “ULTRAPOWER MODE ENABLED!” and enforce mandatory checkpoints per phase; embed the workflow logic directly to ensure continuous phase execution.
  • Show “Ultrapower Mode Activated” toast and set message.variant to max.
  • In non-main sessions, allow Ultrapower and Ultrawork; other keywords are filtered.

• Bug Fixes

  • Prefer session state agent over input.agent to avoid stale agent-driven messages.
  • Skip keyword injection for background task sessions to prevent incorrect mode activation.
  • Enforce word boundaries to avoid false positives (e.g., “ulw” inside other words).

^{Written for commit 1ee8117. Summary will update on new commits.}

[github-actions]

Thank you for your contribution! Before we can merge this PR, we need you to sign our Contributor License Agreement (CLA).

To sign the CLA, please comment on this PR with:

I have read the CLA Document and I hereby sign the CLA

This is a one-time requirement. Once signed, all your future contributions will be automatically accepted.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[cubic-dev-ai]

No issues found across 5 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion

[cubic-dev-ai]

No issues found across 8 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.