spec-driven-promptlisted

# Spec-Driven Prompt Generation Generate bounded work unit specs for agent execution using spec-driven development principles. ## When to Use - RAV discussion with user is complete - Task scope, mode, and expected outcomes are established - Ready to hand off a discrete work unit to an executor agent ## Philosophy **Spec-Driven Development:** Each deliverable has matched validation(s). The agent has full implementation freedom within spec bounds. Define *what* and *how to verify*, never *how to implement*. **Failure Attribution:** Modern coding agents are capable tools. If a task with clear deliverables and clear validations fails, the spec failed. Debug the spec first. **Bounded Work Units:** Each spec represents a discrete, self-contained unit of work. Size varies (small fix to substantial feature), but boundaries are always clear. The agent knows exactly when it's done. **Agent Agnostic:** The spec structure works across executors: Codex, Claude Code, OpenCode, GeminiCLI, or any capable coding agent. The Execution Environment block captures executor-specific details without polluting the spec itself. **Worklog Closure:** Every spec execution produces a matching worklog and is then archived. The spec is not complete until the agent has written the worklog, appended the registry row, and moved the spec into its month archive. This is a deliverable, not optional bookkeeping. ## Naming Convention Specs and worklogs share a naming pattern. Replace `spec` with `worklog