Implement

Implement exactly one work item per session, test-first and verified end to end. A work item is a ticket, a spec small enough for one session, or an agreed conversation scope. The one exception is a spec run, which builds every ticket of a spec in one session.

Spec runs and PR delivery live in references/spec-run.md. Read it before step 1 on every run: its Choose the delivery shape question comes first (current branch, a PR, or a stack of PRs for a whole spec). Its spec-run and follow-up sections apply when the user asks to build a whole spec (all, "implement all of …") or to change work already delivered as a PR.

Pipeline position: wayfinder (decide) → to-spec (write the spec) → to-tickets (break it into tickets) → implement (build one ticket per session, review and verify inside).

Guardrails

• Never reset, roll back, drop, or truncate a database, or run another destructive data operation, without explicit approval. Put schema changes in new migrations; sequence live-table changes expand–contract.
• Verify identifiers before using them: route names, config keys, enum values, icon names, and package APIs. A manifest entry alone does not prove registration or use.

Stack references. Identify the stack from its manifests. If a matching file exists below, read it before step 1: it names that stack's destructive commands, formatter, test command, and worktree setup.

• Laravel (laravel/framework in composer.json): references/laravel.md

Process