Skip to Content
ProjectsUltrapowers

Ultrapowers

A development method your coding agent follows, packaged as a plugin for fifteen coding agents. It sets a project up in one command, then takes every ticket from brief to grounded spec, plan, and tested, reviewed code. You choose how much runs on its own; nothing merges without you.

Why I built it

Every project I set up for a coding agent needed the same things: an instruction file, MCP configuration, a place for specs and plans, a way to keep agents from writing code before anyone agreed what to build. I was copying that setup from the last project and adapting it by hand every few days. And once the setup was there, the teams I work with asked the same question: give the agent a ticket and wait for the pull request, without lowering the bar.

Ultrapowers is the answer to both. The setup is generated, never copied. The method is enforced by skills that trigger on their own. And the automation stops exactly where a team wants a human decision: at the spec and plan, and at the pull request.

Architecture

  • A bootstrap that loads at session start on every harness, so the skills trigger without a prompt.
  • A skills library: brainstorming, writing plans, test-driven development, code review, finishing a branch, the ticket skills and team memory, plus a seven-lane QA specialist (beta).
  • A scaffold engine behind /ultrapowers:init, with scaffold, join, upgrade and repair modes. It shows the file list first and never overwrites a file.
  • An autopilot engine in plain Node with no AI in it: it posts the review packet, verifies your label on the tracker’s own timeline, pushes between stages and opens one pull request per repository. Two doors: a command in a session, and a watcher (beta) that picks up labelled tickets.
  • A guardrail hook that denies the agent a push, a merge, a tracker write, and edits to configuration, CI, hooks and settings during a stage. Plugin hooks on nine harnesses, in-process hooks on three, a project hook for Gemini CLI. It matches patterns; it is not a sandbox.

Proof

The one-command flow ran live on the plugin’s own repository on Claude Code with GitHub: issue 16 became pull request 20. The packet was fifteen lines. An approval label added before the packet changed nothing. Under pressure, the agent refused to add the approve label for itself, both when the request sat in an issue comment and when it was relayed in the prompt.

Every commit runs the offline suites on Linux and Windows: the engine against a fake tracker and a fake harness, the guardrail’s autopilot profile, the in-process hooks, the adapters’ command lines, and the setup engine.

Design rules

  • Zero dependencies. Node built-ins only. No third-party package at run time.
  • No telemetry. The plugin’s own code opens no network connection. When a skill needs the network for your task, it goes through a tool you installed and signed in, to a host you named.
  • Skill bodies are code. Their prose shapes the agent’s behaviour and was tuned against real sessions; changes come with before-and-after evidence.
  • Nothing is written without a yes. Init shows the file list first. Autopilot stops at the packet and at the pull request.
  • One vocabulary. ultrapowers: skills, up: labels, .ultrapowers/ at run time, ULTRAPOWERS_ in the environment.

Ultrapowers is a fork of Jesse Vincent’s MIT-licensed skills library, cut from its version 6.4.2, and is source-available under a proprietary license. Bugs go to the repository’s issues, questions and ideas to its Discussions .

Work with me

Do you want to automate the development workflow of your project with Ultrapowers? Do you want me to set it up on your project, or teach your team how to use it? Contact me.

Last updated on
All Projects