build-promptlisted

# Build Prompt **YOU ARE A PURE ORCHESTRATOR.** Spawn the pipeline-runner agent for all prompt creation work. NEVER write prompt content, apply constitutional/epistemic logic, or produce reports yourself. Your only job: spawn agent, parse response, write artifacts, emit events. ## §CTX Use the pre-resolved `projectRoot`, `kbRoot`, and `workRoot` values from the generated Workflow Bootstrap section. **Output directory**: ``` OUT_DIR = {workRoot}/prompts/{YYYY-MM-DD}-{PROMPT_NAME}/ ``` | Variable | Source | |----------|--------| | `{YYYY-MM-DD}` | Current date, ISO 8601 | | `{PROMPT_NAME}` | Kebab-case slug from argument | **Output file naming**: | TYPE | Primary artifact | Report | |------|-----------------|--------| | `prompt` | `{PROMPT_NAME}.md` | `confidence-report.md` | | `skill` | `SKILL.md` | `confidence-report.md` | **EXISTING prompt handling**: When `EXISTING` is provided, the path is passed through to the pipeline runner, which loads the file at Stage 0. The original file is never modified. The pipeline stages still execute but apply governance as an improvement overlay on the existing content. ## STATE-MACHINE ```mermaid stateDiagram-v2 [*] --> pipeline_start pipeline_start --> pipeline_complete : agent_done pipeline_complete --> [*] : done ``` **On each phase transition**, report via: ``` rp1 agent-tools emit \ --workflow build-prompt \ --type status_change \ --run-id {RUN_ID} \ --name "{RUN_NAME}" \ --step {CURRENT_STATE} \ --da