Project Implement - execute a verified plan, task by task, in one chat

This is the build step of the single-session vertical: project-solution-design produced the plan, project-verify-plan audited it, this executes it - one task at a time, in the plan's dependency order, in your context so every diff is inspectable as it lands. It carries the implementer seat's execution protocol only; the coding conventions themselves need no restating - the path-scoped rules auto-attach the house skill per file type, the generated code-style hook injects the project's actual style on the first edit, and the plan's task cards name the stack traps.

The protocol - per task, in plan order

1. Take exactly one task. Its card is the contract: the files it owns, the traps it names, the file:symbol anchors, and its acceptance criterion. Jump to the anchors - the designer already located them; do not re-navigate the repo.
2. Build the slice + its tests together. The acceptance criterion is what the tests prove; a task without its test is not built, it is drafted. Stay inside the task's boundary - a needed change outside it is a flag, not a detour (see below).
3. Gate the task green. Build + the relevant tests after each task, not at the end of the plan. A red that resists one honest fix attempt routes to the stack's matching build/test resolver agent where the stack ships one (the repair-loop rules name them per file family) - it absorbs the fix loop and returns the diagnosis; trivial reds, and stacks without a resolver seat, fix inline.
4. Close the task honestly - the superpowers:verification-before-completion gate per task: run it, quote the output, then the next task. Partial is stated as partial.

When the plan meets reality

• A task proves wrong mid-build (the seam isn't where the plan said, a trap the audit missed): stop the task, name the delta, and re-enter project-solution-design on that slice - never silently redesign while implementing. The plan is the contract; reality wins, but through a revision, not a drift.
• Scope beyond the plan (a bug discovered nearby, a refactor itch): flag it and ask - it enters the plan explicitly or waits. Never rides along.
• A shared contract surfaces (a DTO both sides compile against, a schema semantic): stop - that is project-task-flow territory, the same BLOCKED_CONTRACT_CHANGE discipline the dispatched seats follow.

Finish - the in-session verifier