cc-project-init

Routes cc-project-init invocations to the standard project-init initialization workflow.

1.0k|109|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill cc-project-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-project-init
Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-project-init-alias
Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-project-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users who invoke the legacy cc-project-init command need it to behave identically to the standard project-init flow without maintaining a duplicate set of initialization rules.

Core Features & Use Cases

  • Compatibility Alias: Redirects explicit cc-project-init calls to the standard project-init process defined in the main skill.
  • Project Scaffolding: Scans the repository, generates or updates a project-level AGENTS.md, and initializes a minimal .codex skeleton (tasks, archived tasks, templates).
  • Scope Guardrails: Does not overwrite existing project files, adds extra scaffolding only on explicit request, and defers README generation to the project-scan skill.
  • Use Case: A developer types $cc-project-init in a new repository and gets the same AGENTS.md and .codex skeleton that $project-init would produce.

Quick Start

Invoke $cc-project-init in your repository to run the standard project-init flow that creates AGENTS.md and the minimal .codex directory skeleton.

Frequently Asked Questions about cc-project-init

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

FAQPage Schema
How do I initialize a project with AGENTS.md and a .codex skeleton?▼

Invoke $cc-project-init or $project-init in the repository. The flow scans the current repo state, generates or updates a project-level AGENTS.md, and creates .codex/tasks, .codex/tasks/archived, and .codex/templates directories.

What is the difference between cc-project-init and project-init?▼

cc-project-init is a compatibility alias with no separate logic. It delegates entirely to the standard project-init flow, so both commands produce identical results and share one set of initialization rules.

Does project initialization overwrite my existing project files?▼

No. The initialization flow reads the current repository state first and does not overwrite existing project files. Additional scaffolding files are only added when the user explicitly requests them.

Can cc-project-init generate or refresh my README.md?▼

No. README generation belongs to the project-scan skill, not project-init. When a README refresh is expected, the alias explains this boundary and suggests running $project-scan next.

Why does cc-project-init not run automatically in my session?▼

The alias policy sets allow_implicit_invocation to false, so it only runs when explicitly invoked by name. This prevents unintended repository scaffolding during unrelated tasks.