Skip to content

keithhegit/ultra-orchestration / skills-vnext/ultra-planning

ultra-planning

Verified

Rigid decision-complete planning for Codex Ultra vNext. Use after intake, brainstorming, or OpenSpec bridge whenever work spans multiple files, roles, phases, or risk boundaries and must be turned into review-ready TaskManifest and WorkPackage artifacts with explicit dependencies, owned paths, acceptance checks, retry assumptions, and serial versus parallel execution rules.

references/planning-anti-patterns.md

View on GitHub
# Planning Anti-Patterns

## Bad Plan Signals

- the plan says "implement as needed" without file ownership
- acceptance checks are vague, such as "works correctly"
- several packages can write to the same path without a lock decision
- review is expected to infer intent from chat history
- QA has no scenario list
- a worker must make architecture decisions during implementation

## Example: Too-Broad Owned Paths

Bad:

- `owned_paths: src/`

Better:

- `owned_paths: src/runtime/summary.ts`
- `owned_paths: src/renderer/panels/runtime-panel.tsx`

## Example: Weak Acceptance Checks

Bad:

- "state should work"

Better:

- "bootstrap response includes runtime summary"
- "renderer can show current phase without parsing chat prose"

## Example: Unsafe Parallelism

Bad:

- two packages both write `src/runtime/summary.ts`

Better:

- either merge them into one package
- or serialize them with an explicit dependency
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall