ultraplan-codex

Generate file-path-verified implementation plans from repository exploration.

18|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dachent/skills --skill ultraplan-codex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultraplan-codex
Source: https://github.com/dachent/skills/tree/main/ultraplan-codex
Command: npx skills add https://github.com/dachent/skills --skill ultraplan-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of poorly defined implementation plans by enforcing a rigorous, read-only exploration phase that ensures architectural decisions are grounded in actual repository state before any code is written.

Core Features & Use Cases

  • Durable Planning: Creates a standardized .ultraplan/plan.md file that serves as a single source of truth for the implementation.
  • Grounded Exploration: Automatically scans the codebase to identify existing utilities, patterns, and dependencies to reuse, preventing redundant work.
  • Adversarial Review: Supports high-risk change validation by comparing proposed plans against architectural best practices and potential failure modes.

Quick Start

Invoke the ultraplan-codex skill to generate a comprehensive implementation plan for your current task by providing the feature requirements in your prompt.

Frequently Asked Questions about ultraplan-codex

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

FAQPage Schema
How do I generate an implementation plan for a complex codebase refactor?

To generate an implementation plan for a complex codebase refactor, use a read-only exploration phase that scans repository files and git metadata to synthesize a dependency-safe execution sequence grounded in the actual architectural state.

What is grounded codebase exploration before feature implementation?

Grounded codebase exploration is a read-only scanning process that identifies existing utilities, patterns, and dependencies to reuse, preventing redundant work and ensuring architectural decisions match the actual repository state.

Does this implementation planning approach modify my existing repository files?

No, this implementation planning approach requires only read-only access to your repository files and git metadata to synthesize actionable execution sequences without modifying your existing codebase during the exploration phase.

How do I validate high-risk architectural changes against failure modes?

You validate high-risk architectural changes by applying an adversarial review process that compares proposed implementation plans against architectural best practices and potential failure modes before any code is written.

What is the best way to maintain a single source of truth for software development tasks?

The best way to maintain a single source of truth is to generate a standardized plan.md file within a dedicated directory, serving as a durable reference for the entire implementation workflow.