Implement

1. Read the requested spec or tickets and state their identity, accepted scope, and test seams. If a reference is ambiguous, ask. Resolve the project's shared artifacts through /domain-modeling; consume them without reopening settled decisions. Invoke /principles for implementation before code changes. Complete when the work, applicable design constraints, and its done predicate are grounded in the existing source of truth.
2. Implement vertical slices through /tdd where a useful test path exists. Reuse agreed seams and repository checks; run typechecking and single test files regularly. Use /swarm only for useful bounded delegation, with isolated writers and one coordinator for canonical docs; explicitly pass /principles and the resolved applicable owners to writers. Recheck selection when the work reveals a new branch. Complete each slice when its observed behavior satisfies its acceptance criteria and applicable rules.
3. Reconcile accepted domain changes through /domain-modeling and inspect the full diff. Recheck /principles for verification, run the full test suite once and other relevant checks, and invoke /review-loop for the final artifact, reusing valid review evidence supplied by the caller. Resolve actionable findings; when a fix changes the reviewed artifact, refresh the affected review coverage and checks. Complete when implementation, docs, acceptance evidence against the actual artifact, and review findings agree at the delivered revision or a gap is explicit.
4. Commit the scoped result to the current branch when authorized and prepare a draft PR when requested or part of the existing grant. Invoke /pr for its description. Keep tracker closure tied to the project's actual completion boundary. Complete when the result is reviewable and delivery state is truthful.