Initialize a project

Initialization is the one step you run yourself before day-to-day management through a coding agent. From the project you want to configure:

cd /path/to/your-project
agents-pack init

Agents Pack asks you to choose:

• repository or global scope;
• Claude Code, Codex, Cursor, or a supported combination; and
• Recommended, All, or a custom component selection.

It shows the exact selected components and filesystem plan before applying anything. Pressing Enter at the confirmation prompt does not apply the plan; you must answer y or yes.

Interactive setup

Use the arrow keys to move through each menu. Press Space to toggle agents or components, and Enter to confirm the visible selection. Repository scope, all compatible agents, and recommended components are selected by default.

Non-interactive setup

To install the recommended repository components for all three agents:

agents-pack init \
  --scope repository \
  --agents claude,codex,cursor \
  --components recommended \
  --yes

--agents all is shorthand for --agents claude,codex,cursor.

For a global Claude Code and Codex installation:

agents-pack init \
  --scope global \
  --agents claude,codex \
  --components recommended \
  --yes

To apply an initialization from a script or another non-interactive shell, provide the scope, agents, component choice, and --yes. Use --dry-run instead of --yes when the script should only print the plan.

Preview first

Content-changing commands support a dry run:

agents-pack init \
  --scope repository \
  --agents claude,codex,cursor \
  --components recommended \
  --dry-run

A dry run loads and validates the pack and prints the same plan, but does not write provider files, installation state, transaction state, or the pack cache.

Component selection

The core pack labels components as required, recommended, or optional.

Choice	What it installs
recommended	Every required and currently recommended component. Best starting point for most users.
all	Every compatible component in the current pack version. One-time expansion, not a subscription — later optional components are not silently installed.
Explicit IDs	A tailored list such as ap-debug,ap-code-reviewer,ap-frontend-design. Required components are added automatically.

During interactive initialization, choose custom to start from the Recommended set and toggle components by ID or category. Your final component IDs are stored explicitly.

See Component selection and the skill catalog for more detail.

Use an explicit local pack

init normally uses the official registry. For development, private content, or air-gapped work, pass a directory:

agents-pack init \
  --scope repository \
  --agents claude,codex,cursor \
  --components recommended \
  --pack /path/to/local-pack \
  --yes

The installation records whether its source is official or local. A local installation never silently switches to the public registry.

After initialization

Coding agents discover the installed instructions, skills, and subagents through their native mechanisms. Check health with:

agents-pack status

Before your first real task, set up the opinionated workflow: a PRD.md, TECHNICAL_REQUIREMENTS.md, and TODOs.md at the repository root that the installed core instructions read automatically at the start of every session.

Then try first workflows — usually by asking your coding agent what you want next.

For every flag and option, see the CLI reference.