ultraplan
Ultraplan cloud planning — kick off a plan in the cloud from your terminal, review and revise in the browser, then execute remotely or send back to CLI
What this skill does
# Ultraplan Ultraplan offloads plan mode to the cloud. Claude drafts the plan in a Claude Code web session while your terminal stays free. You review sections in your browser, comment, request revisions, then choose to execute remotely or send it back to your CLI. Available since v2.1.92 (research preview). As of v2.1.101, the first run auto-creates a default cloud environment — no web setup step required. ## When to Use Ultraplan | Scenario | Use Ultraplan | Use Local Plan Mode | |----------|:---:|:---:| | Complex multi-service migration | ✓ | | | Need to share plan with teammates | ✓ | | | Terminal must stay free during planning | ✓ | | | Quick single-file refactor | | ✓ | | No internet / air-gapped environment | | ✓ | | Iterating rapidly on small tasks | | ✓ | ## Usage ### Via slash command ``` /ultraplan migrate the auth service from sessions to JWTs ``` ### Via natural language Include the keyword "ultraplan" in any prompt: ``` > ultraplan: design the database migration strategy for the multi-tenant switch ``` ### What happens 1. Claude Code sends the task to a cloud session 2. Your terminal shows a link and returns immediately 3. In your browser: Claude drafts the plan with sections, code snippets, and decision points 4. You comment on individual sections, ask for revisions, accept or reject sub-plans 5. Choose **Execute in cloud** or **Send to CLI** when satisfied ## Reviewing and Revising The browser interface shows the plan as structured sections: - Comment on a specific section to request a change - Ask for a complete alternative approach - Accept sections one-by-one or all at once Plan history is preserved — you can compare revisions and revert. ## Execution Options ### Execute in cloud (remote) Claude Code on the web runs the implementation. Results and changed files are available in the session. Push from the web session or download a patch. ### Send to CLI The approved plan is serialized and sent back to your local terminal session. Claude continues from there with the agreed plan as context. ## /autofix-pr Integration After executing in the cloud and pushing a branch, use `/autofix-pr` to hand the PR over to Claude: ``` > /autofix-pr ``` Claude detects the open PR for your current branch and enables auto-fix — watches CI, fixes failures, handles review comments, pushes until green. ## Cost and Model Ultraplan uses Opus (`opus` → latest `claude-opus-4-8`) by default for the planning phase — the reasoning depth justifies the cost for complex migrations and architectural decisions. Pair it with a high `effort` level (`xhigh`/`max` on Opus 4.8) for the hardest plans. The execution phase uses the model appropriate to the task. Estimated cost for a complex plan: ~$0.50–$2.00 depending on context volume. Simple plans use fewer tokens and run faster. ## Pairing with /team-onboarding Use ultraplan to design a feature, then run `/team-onboarding` to generate a ramp-up guide that explains the resulting architecture to new teammates: ``` > /team-onboarding ``` This generates a guide from your local Claude Code usage patterns and the project structure — useful after landing a large feature.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.