Organize Codex Projects
SkillDev toolsChoose a location and internal structure for a future Codex project, including focused projects and umbrella projects with durable subprojects. Use when creating or planning a new project. Do not move, rename, or normalize existing projects.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Organize Codex Projects skill
What this skill tells your AI
The instructions your AI receives, as published by wildpigking/codex-project-skill-manager in .agents/skills/organize-codex-projects/SKILL.md and read by ahel’s review.
Resolve the approved future-projects root before creating anything.
For a focused project, create AGENTS.md, README.md, data, temp, output, docs/ai/dev_log.md, and docs/ai/experience_candidates.md. Add src and tests only when code benefits from them.
Use an umbrella project only when two or more workstreams have meaningfully independent goals, inputs, outputs, or lifecycles. Keep shared material at the umbrella root and give each durable subproject its own README, data, temp, and output boundary. File count alone is not a reason to split.
Use concise purpose-derived names. Do not add date wrappers, random abbreviations, final, or numeric collision suffixes. If a target exists and reuse is unclear, stop and ask.
Keep original inputs in data, reproducible intermediates in temp, and current deliverables in output. Never silently overwrite source material.
Return the resolved absolute target and a structure preview before writing.
Signals
- GitHub stars
- 22
- Forks
- 1
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
organize-codex-projects- Source
- github.com/wildpigking/codex-project-skill-manager