Getting Started

Install the Plugin

In any Claude Code session, run these two commands:

# Add the marketplace
/plugin marketplace add duniecdawid/ultra-claude-code

# Install the plugin
/plugin install uc@ultra-claude

All skills become available as /uc:* slash commands.

Set Up Your Machine

Run this once to configure your environment:

/uc:setup

This installs prerequisites (Node.js, optionally tmux), guides you through tmux mode selection, configures your shell for 1M context and agent teams, and sets up the layout manager when tmux is enabled. Idempotent — safe to run again if anything changes.

Initialize Your Project

Navigate to your target project and run:

/uc:migrate

This scaffolds documentation/, explores your codebase, derives configuration files, drafts initial architecture docs, and generates coding standards from detected patterns.

Review Your Documentation

Migrate generated architecture docs, coding standards, and testing configuration from your codebase. Take a few minutes to review them — every planning skill reads these docs to make informed decisions about scope, conflicts, and architecture classification.

• documentation/technology/architecture/ — system design derived from your codebase
• documentation/technology/standards/ — coding conventions detected from your patterns
• documentation/technology/testing/ — test strategy and commands

The more accurate these are, the better the plans. Learn about standards enforcement →

Plan Your First Feature

Run feature mode with a description of what you want to build:

/uc:feature-mode add user authentication

Feature mode acts as a senior tech lead. It challenges your scope, researches your codebase in parallel, and produces a structured plan with end-to-end testable tasks before any code is written.

• Scope challenge — asks "why?", splits vague requests, refuses to plan until scope is sharp
• Codebase research — spawns agents to explore existing patterns and find conflicts
• Structured plan — tasks with file lists, success criteria, and dependencies in documentation/plans/

Review and approve the plan before execution. Read more about feature planning →

Execute

/uc:plan-execution {plan-name}

The execution engine spawns a dedicated team for each task: an Executor that writes code, a Reviewer that enforces your standards, and a Tester that validates against product docs. The Lead brokers external library knowledge via the /uc:research skill (cache-first, writes committed research files under documentation/technology/research/), and a Project Manager monitors progress.

Sessions can die and resume — checkpoints save progress automatically. Read more about plan execution →