codex-plans

Create and execute structured design documents for complex software features.

3|Updated May 26, 2026
One-click install
npx skills add https://github.com/aurabx/nightowl --skill codex-plans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-plans
Source: https://github.com/aurabx/nightowl/tree/main/.agents/skills/codex-plans
Command: npx skills add https://github.com/aurabx/nightowl --skill codex-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent or poorly defined feature development by providing a rigorous, self-contained framework for creating execution plans that any agent or developer can follow.

Core Features & Use Cases

  • Self-Contained Design: Ensures every plan contains all necessary context, definitions, and instructions, eliminating reliance on external memory or prior knowledge.
  • Milestone-Driven Development: Forces the breakdown of complex tasks into verifiable, incremental steps that prove progress through observable outcomes.
  • Decision Logging: Maintains a clear history of design choices and discoveries, ensuring that future contributors understand the rationale behind the current implementation.

Quick Start

Use the codex-plans skill to generate a new execution plan for the upcoming refactor of the DICOM listener module.

Frequently Asked Questions about codex-plans

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

FAQPage Schema
What is the best way to standardize complex software feature development for coding agents?

Standardizing complex software feature development requires creating rigorous, self-contained execution plans that provide a structured, verifiable roadmap, ensuring maintainability and clarity for coding agents.

How do I create an execution plan for refactoring a software module?

Creating an execution plan for refactoring requires generating a self-contained design document that breaks down complex tasks into verifiable, incremental milestones to prove progress through observable outcomes.

Why do I need decision logging in my technical documentation?

Decision logging in technical documentation maintains a clear history of design choices and discoveries, ensuring that future contributors understand the rationale behind the current implementation.

Does milestone-driven development work for complex refactoring tasks?

Milestone-driven development works for complex refactoring tasks by forcing the breakdown of work into verifiable, incremental steps that prove progress through observable outcomes.

When should I not use self-contained design documents for feature development?

You should avoid self-contained design documents for feature development when tasks are simple enough to not require a structured roadmap, or when strict formatting and milestone tracking would create unnecessary overhead.