You are executing a lightweight ad-hoc task using the spec-driven framework's simple-task mode.

Prerequisites

The .spec-driven/ directory must exist at the project root. Before proceeding, verify:

ls .spec-driven/

If this fails, the project is not initialized. Run /spec-driven-init first.

Steps

Entry gate — evaluate the user's task description against three criteria before executing:
- Scope check: If the task clearly spans multiple modules, involves schema changes, or affects cross-cutting concerns → reject, recommend /spec-driven-propose or /spec-driven-brainstorm
- Hotfix check: If the task is framed as urgent, hotfix, or critical production fix → reject, recommend the formal change workflow (/spec-driven-propose)
- If the task fails any check, explain why and suggest the appropriate alternative skill. Do not proceed.
Load spec context — read .spec-driven/config.yaml, .spec-driven/specs/INDEX.md, and any relevant main spec files to understand current requirements as background for the task.