uberplan

Create long-running engineering plans with scope fidelity and evidence-backed proof gates.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/rdleclerc/agentic-uber-skills --skill uberplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uberplan
Source: https://github.com/rdleclerc/agentic-uber-skills/tree/main/uberplan
Command: npx skills add https://github.com/rdleclerc/agentic-uber-skills --skill uberplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

uberplan turns ambiguous, long-running engineering work into a safe, verifiable plan that prevents scope drift, symptom-patching, and false completion.

Core Features & Use Cases

  • Long-running goal planning with gates: defines checkpoint cadence, verification proof gates, and a durable Definition of Done so the plan can’t “look finished” without evidence.
  • Scope fidelity and operational completion: requires a Scope Fidelity block and an Operational Outcome Contract with allowed terminal states (operational/blocked/re_scoped_with_approval).
  • Agentic-system safety for planning: adds adversarial review lanes (Agent Advocate RCA, Architecture Steward, First-Principles Simplifier) and mandates an Evidence/Black-box proof pattern where relevant.

Quick Start

Use uberplan to plan a long-running coding goal with scope fidelity, a Definition of Done, user expectation/surprise assessment, and evidence-backed proof gates for completion.

Frequently Asked Questions about uberplan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create verifiable execution contracts for long-running coding plans?

Scope fidelity prevents scope drift in agentic workflows by requiring a dedicated Scope Fidelity block, blocking overbroad or under-evidenced plans through a confidence gate before execution begins.

What is an Operational Outcome Contract and when do I need it for refactoring?

An Operational Outcome Contract defines allowed terminal states like operational, blocked, or re_scoped_with_approval. You need it for refactoring and production-risk work to prevent symptom-patching and false completion.

How do I set up testing adaptation gates and proof ladders for engineering plans?

Testing adaptation gates and proof ladders verify completion through an Evidence/Black-box proof pattern, establishing checkpoint cadence and a durable Definition of Done so plans require evidence at each gate.

Can I use this planning approach for agentic systems and production-risk work?

Yes, this planning approach suits agentic systems and production-risk work by adding adversarial review lanes including an Agent Advocate RCA, Architecture Steward, and First-Principles Simplifier to ensure safety.

When should I not use automated planning for vague engineering work?

You should avoid automated planning when work must not be auto-sliced by similarity, requiring instead scope fidelity and evidence-backed proof gates to safely convert vague work into verifiable contracts.