// Implement a single phase of a spec. Use when given a spec file and a phase number to implement.
Interact with the running VSCode extension via Playwright. Use when automating, testing, or debugging the OpenCode webview UI.
Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.
Browser automation CLI using Playwright. Use when automating browser workflows, filling forms, clicking elements, scraping pages, or debugging web issues.
Review a spec for under-specified areas, bugs, and adherence to the generate-spec skill. Use when asked to review, critique, or check a spec.
Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
| name | implement-spec |
| description | Implement a single phase of a spec. Use when given a spec file and a phase number to implement. |
Implement the specified phase of the given spec file.
Ultrathink. Follow these steps:
Read the entire spec file. Understand the problem overview, solution overview, goals, and non-goals. Pay close attention to the phase you've been asked to implement.
Read every file listed in the "Important files/docs/websites for implementation" section of the spec. Also read any external documentation links. Do not start writing code until you thoroughly understand the existing codebase and how your changes fit in.
Work through every task item in the phase, including all success criteria (tests, typechecks, lint checks). A phase is not complete until every task item is done, including running any verification steps.
Run pnpm run typecheck, pnpm test, and pnpm run lint after implementation to catch issues.
Check the spec's Goals section. If the phase you just implemented should complete any of those goals, explicitly verify them through integration tests or manual testing of the Electron app using Playwright (see AGENTS.md for Playwright instructions). Do not consider the phase done until achieved goals are verified end-to-end.
Mark all completed task items in the spec as done (- [x]) before presenting to the user.
When you're done, do not stage or commit your changes. Present the completed work to the user for manual review. The user may request changes.
If the user asks for changes, implement them. Iterate until the user is satisfied.
Once the user approves and asks you to commit:
If during implementation you identify work that is not blocking but would be valuable later (big features, refactors, cleanup), propose adding it to a "Future work" section in the spec, placed above the "Important files" section. Confirm with the user before adding.
If the work is blocking (the app is broken without it), it should be done as part of the current spec — either in this phase or added to a subsequent phase.
When the user asks you to hand off to the next phase, include in the handoff summary a note to load the implement-spec skill.