speckit-implement

name	speckit-implement
description	Execute the tasks.md generated by speckit-tasks, running lint/typecheck/tests per task and surfacing blockers, ending with a PR-ready branch for the pickup-points-modal.
type	skill

speckit-implement

Execution of the tasks listed in tasks.md. Structured variant of the implementing skill, tied to the Full Golden Path.

When to use

• specs/<slug>/tasks.md approved.
• The user says "/speckit-implement" or "execute the tasks".

Flow

For each task in tasks.md:

1. Mark it as in_progress in TodoWrite.
2. Read the relevant files.
3. Edit.
4. Run yarn lint --fix in scope.
5. Run yarn test over the affected scope.
6. Mark as completed. Only one task in_progress at a time.

When all tasks are done:

• yarn lint globally
• yarn lint:ts
• yarn lint:locales if i18n was touched
• yarn test
• yarn build
• Compose commits with speckit-git-commit
• Open the PR

Signals to pause and report

• A previously-passing test starts failing outside of the task's scope.
• Lint complains about a file you did not touch (likely a rule change — surface it before mass-fixing).
• yarn build fails due to types in legacy JS code — escalate.

Constitution gates

Before opening the PR, validate:

Principle	Check
1 — backward-compat	PickupPointsModal public props/events unchanged (or major bump documented).
2 — tested behavior	Each behavior task has a new test.
3 — i18n	yarn lint:locales passes.
4 — performance	No new dep > 50KB without dynamic import.
5 — side-effect free	New utilities are pure.