spec-workflowlisted

# OpenSpec Workflow Orchestration Spec-driven development protocol for coordinating multi-agent workflows. ## UUID Enforcement **CRITICAL**: The `conversation_id` MUST always be a UUID (format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`). NEVER use descriptive names, slugs, or human-readable strings. If no UUID is available, generate one with `uuidgen` or `python3 -c "import uuid; print(uuid.uuid4())"`. Self-check: does the conversation_id match the pattern `[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}`? If not, STOP and use a real UUID. ## Directory Structure ``` .scaffolding/conversations/{conversation_id}/specs/ proposal.md -- WHY + WHAT (analyst) design.md -- WHAT + HOW (architect) tasks.md -- checklist (architect) ``` ## Status Lifecycle Tracked in `.scaffolding/conversations/{conversation_id}/context.json`: | Status | Meaning | Transition | |--------|---------|------------| | `exploring` | Research phase | -> `drafting` when proposal done | | `drafting` | Design + tasks | -> `implementing` when tasks done | | `implementing` | Code changes | -> `reviewing` when tasks complete | | `reviewing` | Verification | -> `complete` when verified | | `complete` | Done | -> `archived` on request | | `archived` | Historical | Terminal state | ## Agent Routing in /workflow | Phase | Agent | Reads | Writes | Gate | |-------|-------|-------|--------|------| | 1. Analyze | analyst | requirements | `proposal.md` | proposal written | | 1b. Research (c