[Phase 3] Spec Kit: Specify → Clarify

[jeremymanning]

Summary

Produce a concrete spec.md and resolve all NEEDS-CLARIFICATION markers.

What this phase does

Specifier drives /speckit.specify to produce spec.md (functional requirements + success criteria + user scenarios). Clarifier drives /speckit.clarify to resolve every [NEEDS CLARIFICATION] block.

Project lifecycle stages handled

• specified
• clarified

Dependencies

• Depends on: [Phase 2] Project Bootstrap #46
• Blocks: [Phase 4] Spec Kit: Plan → Tasks (with Analyze loop) #48

Agents in this phase

• sub-issue: specifier ([Agent · Phase 3] specifier #64)
• sub-issue: clarifier ([Agent · Phase 3] clarifier #63)

Manual test plan (phase-level smoke test)

1. Stage a project at the entry stage of this phase (see "stages handled" above)
2. python -m llmxive run --project <PROJ-ID> --max-tasks N (N = number of agents in this phase)
3. Verify the project transitions through every stage listed above
4. Run each agent's manual test plan (linked via the sub-issue checklist)
5. Verify state ends at the entry stage of the next phase, or human_input_needed/blocked on legitimate failure (never silently stuck)

Acceptance criteria (phase-level)

• Every agent sub-issue passes its acceptance criteria
• Phase-level smoke test passes end-to-end on a fresh project
• No silent shortcuts — agents that can't do their work MUST fail loudly (write human_input_needed.yaml or emit verdict: failed), not mark tasks [X] with placeholder content
• All artifacts written by this phase pass schema validation (where applicable)
• Run-log entries record outcome, started_at, ended_at for every agent invocation