Project Initialization Skill
Usage
code
/init [path] [--discover|--generate|--full|--quick|--sync|--update]
Parameters
| Mode | Input | Output | Use When |
|---|---|---|---|
--full | None | .codex/ + DISCOVERY + Docs + Phases | New project (RECOMMENDED) |
--discover | None | DISCOVERY.md | Idea stage only |
--generate | DISCOVERY.md | PRD + TECH-SPEC + PROGRESS + CONTEXT | After discovery |
--sync | .codex/ | Merged .codex/ | Existing project |
--update | None | Updated ultra-codex-init + sync | Framework update |
--quick | Code | AGENTS.md | Quick context |
Examples
bash
/init --full # Full workflow (NEW PROJECT) /init --discover # Discovery conversation only /init --generate # Generate from existing DISCOVERY.md /init --sync # Sync framework to existing project /init --update # Update ultra-codex-init + sync /init ./my-project --full # Initialize specific path
Workflow Chain
code
/init --full → Framework Setup → Discovery → Confirmation → Generate → Phase Split /init --sync → Analyze .codex/ → Merge missing → Validate → Report /init --update → Locate source → git pull → Sync → Report
Critical Rule
For new projects, ALWAYS start with discovery. Never generate docs without understanding.
Full implementation: Load references/DETAIL.md for mode details, step implementations, decision flow, best practices, integration points, and framework sync details.