init-project
Runs the interview of a project's first generation in the main session, then hands the whole generation to one agent.
init-project, section by section
The sections of the skill's own SKILL.md, excerpted. Hover or click one to see which project rules, templates and references/ files it cites. The sections are also chips: click one to jump to it.
## Available blueprints
!find "${CLAUDE_PROJECT_DIR:-.}/.claude/blueprints" -mindepth 2 -maxdepth 2 -name '*.yaml' 2>/dev/null | sort
## Next to this repository
!ls -a "${CLAUDE_PROJECT_DIR:-.}/.." | head -30
## Session
${CLAUDE_SESSION_ID}
## Arguments
$ARGUMENTS
## Procedure
- The project is generated next to this repository, at
../<artifactId> - Interview — every question of the run, here, before delegating. The agent runs in the
… cut here, the rest is in the file
## Why this is a manually-invoked skill
Form 2: creating a project is a ritual a person starts (axis 2 — /init-project), and the interview it leads to cannot be triggered by inference from a sentence. Form 1 was rejected for exactly that: a skill that can scaffold a whole tree on the model's own judgment is a directory rewritten by accident. Form 3 was rejected here and used one level down instead — the isolation belongs to the generation, which is why project-initializer exists, and the interview belongs here, in the main session, the only place AskUserQuestion is guaranteed (@.claude/decisions/0123-lessons-learned-020-init-project-run.md).
Runs on sonnet with effort: low: the interview reads its questions from the blueprints and from the two chained skills, and the generation is delegated to project-initializer, which declares its own model (@.claude/decisions/0081-skill-model-required-per-class.md).
What it reads, writes and refuses
The skill's own contract, from SKILL.md, in the original wording.
Class
orchestrator — the territory is skill_classes.orchestrator's override for this skill in @.claude/schemas/extensions.json, and it is empty: this skill writes no file itself. Everything is written by project-initializer, which the guard bypasses as an executor agent, and by project-bootstrap under it. ArchHook.java guard enforces it. The one write it causes is audit genesis replacing three placeholders in the generated project's GENESIS.md, outside this repository — done by the hook's code, never by a Write.
Reads
the blueprint listing and the listing of this repository's parent directory injected above, every blueprint YAML for the interview, the § 2 questions of transport-security-setup and sonarqube-setup, and the arguments.
Owns
the interview of a project's first generation. The questions about transport and Sonar stay owned by their skills; this one only asks them before the agent starts.
Delegates
to project-initializer — never generates a file inline, not even a single pom.xml. A partial generation from this thread is the failure mode the agent exists to prevent: the report would describe a tree nobody wrote in full.
Source: SKILL.md § Contract, at nerviz e4cae27.
What the guard does with it
orchestrator is the skill's class, and its territory is empty: it writes no file itself. The phase it opens is what stops a generation from happening in the main thread. The text on the right is the hook's own.
write_allow of class init-project
any file: the territory is empty
A refusal exits with code 2 and the message goes back to the model.
> /init-project … UserPromptSubmit guard prompt exit 0 # phase opened: init-project (class orchestrator) # write_allow: [] — this skill writes no file itself
PreToolUse Write(../bank-app/pom.xml) guard write exit 2 ❌ `init-project` is class `orchestrator` — ../bank-app/pom.xml is outside its territory. write_allow: (nothing — this class writes no file) Put the content in the spec as a code block, or finish the run and invoke the skill that owns this path. If the path is legitimately this skill's, widen skill_classes.orchestrator in .claude/schemas/extensions.json — retrying will not help.
PreToolUse Agent(project-initializer) guard call exit 0 # an Agent call changes nothing here: the phase stays init-project PreToolUse Write(../bank-app/pom.xml) # agent_type: project-initializer guard write exit 0 # judged by agent_classes.driver, write_allow: **
Where it sits on the rail
Each card is a step of /init-project. The interview runs in the main session; the tinted steps run inside project-initializer; git-publish comes back to the main session, after audit genesis. Dashed steps run only when they apply.
/init-project orchestrator · sonnet