[Agent · Phase 2] project_initializer

[jeremymanning]

Parent phase: #46

Purpose

Bootstrap a per-project Spec Kit scaffold and render a project constitution.

What it produces / drives

Creates projects/<PROJ-ID>/.specify/{constitution.md,memory/,scripts/bash/,templates/} and ensures the directory layout subsequent slash commands expect.

Dependencies

This agent depends on output from: idea_selector

Acceptance criteria

• Renders .specify/memory/constitution.md with project-specific principles (not template placeholders)
• Creates the scripts/bash/ runners (setup-plan.sh, check-prerequisites.sh, etc.)
• Idempotent: running twice doesn't duplicate or corrupt files

Manual test plan

1. Create a fresh project with state flesh_out_complete
2. python -m llmxive run --project <PROJ-ID> --max-tasks 1
3. ls projects/<PROJ-ID>/.specify/ — must have constitution.md, memory/, scripts/, templates/
4. Open constitution.md — must reference the project title and idea, NOT generic template text

Implementation pointer

• Registry entry: agents/registry.yaml → name: project_initializer
• Prompt: agents/prompts/project_initializer.md
• Code: search src/llmxive/ for the class

[jeremymanning]

Status update: PR #109 verifies all 3 acceptance criteria pass on PROJ-261-iter3 + PROJ-262-iter3 (constitution rendering, scripts/bash runners, sha256-byte-idempotent). Two iter3 constitutions pass the full 6-item US2 audit cleanly under prompt v1.1.0. Will close after merge.

[jeremymanning]

Resolved via spec 004 (PR #109, merge commit a00b01e). Phase 2 project_initializer agent verified end-to-end on canonical PROJ-261 + PROJ-262. All 3 acceptance criteria pass per § 6 of notes/2026-05-05-phase2-diagnostic.md. Carry-forward manifest at specs/004-phase2-project-bootstrap-testing/carry-forward.yaml names both canonicals as substrate for spec 005.