organize-codex-projects
Choose 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.
WildPigKing · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add WildPigKing/codex-project-skill-manager --skill organize-codex-projects技能说明
name: organize-codex-projects description: Choose 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.
Organize Codex Projects
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.