Implement

human-only. Start this only when a human asks for it by name. If you arrived here from another skill, stop and get explicit confirmation before running any step.

The last step of the pipeline: /wayfinder charts the decisions, /decisions-to-specs settles them into specs, /specs-to-tickets slices those into build tickets, and this skill builds one. The ticket and its specs are the plan — this skill does not re-decide them, and a ticket that still needs a decision belongs back on the map, not here.

Implement the work described by the user in the spec or tickets.

Adapted from Matt Pocock's /implement; the build method — TDD at pre-agreed seams, the test cadence, the /code-review pass before committing — is his. Steps 1 and 2 are this repo's addition.

Where the work is based is decided before it is written. Steps 1 and 2 are not setup to be hurried through: a session that starts typing in the primary checkout has already committed to a base nobody chose, and no amount of good building fixes that afterwards.

Process

1. Settle the base before creating anything

The default base is a freshly fetched origin/main — never the local main, never the current HEAD. Sessions share the primary checkout, so whatever it is sitting on is nobody's chosen base, and the local main is only as old as the last pull. Either one silently makes someone else's work the base of yours, and it surfaces later as a PR diff full of commits this ticket never touched.

origin/main is the default, not the only option. Work that needs a change still sitting in an open PR belongs on top of that PR. Base it on main anyway and you either rewrite what that PR already did or write against files it is about to move.