phase-development

Organizes software projects into phases and loads context, specs, and task lists.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/tygwan/ultra-codex-init --skill phase-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-development
Source: https://github.com/tygwan/ultra-codex-init/tree/main/.codex/skills/phase-development
Command: npx skills add https://github.com/tygwan/ultra-codex-init --skill phase-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase-based development helps teams structure work around clearly defined phases, enabling predictable planning and progress visibility across projects.

Core Features & Use Cases

  • Phase planning: load phase SPEC and TASKS, track progress via PROGRESS.md, and transition to the next phase.
  • Context-aware work: load CONTEXT.md to keep context aligned across sessions.
  • Dependency-aware execution: ensure tasks in a phase respect prerequisites before starting.

Quick Start

Load the current phase SPEC and TASKS, then begin with the first task.

Frequently Asked Questions about phase-development

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

FAQPage Schema
How do I track development progress across multiple project phases?

Track development progress across multiple phases by loading phase-specific SPEC and TASKS documents, then updating PROGRESS.md to reflect the current phase status and completed work.

What's the best way to organize phase-based software development workflows?

Organize phase-based software development workflows by structuring work into defined phases, loading docs/phases/phase-N/SPEC.md and TASKS.md, and maintaining docs/CONTEXT.md for cross-session alignment.

How do I ensure task dependencies are respected before starting a new phase?

Ensure task dependencies are respected by loading the current phase TASKS.md to verify prerequisites are met before execution, preventing out-of-order task completion within a phase.

Can I maintain project context across different development sessions?

Maintain project context across different development sessions by loading docs/CONTEXT.md, which keeps context aligned and ensures continuity between separate work periods on the same phase-based project.

Does phase-based development work for projects with complex task dependencies?

Phase-based development works for projects with complex task dependencies by organizing work into defined phases, applying dependency-aware execution, and tracking ongoing progress through structured markdown documentation.