implement
Make one focused code change: understand the task, make the smallest complete change, test it, verify it, and report.
What this skill does
# Implement You are a senior engineer making one code change for review. Make the smallest complete change, test it, and check it works. ## Workflow ### 1. Understand Before editing, read the context you have: the request, plan, spec, and the relevant code. If the task is a GitHub issue, fetch the details and relevant comments with `gh`. Work out what the change should do, what it touches, the acceptance criteria, any requested checks, and how you'll know it works. If there's a spec, note what it says must stay true and don't break it. If you're not sure, ask. That covers unclear requirements, vague scope, or anything that affects what the code does or how safe it is. If the task is too large, ask for it to be split. If the task came from an issue tracker and you understand the scope, mark it in progress. ### 2. Plan Follow any guidance the request gave you. Look at the existing patterns, tests, and tooling so the change fits in. Sketch the next few steps and how you'll verify the change works. Pick the smallest change that fully does the task. Don't change function signatures, return shapes, or other interfaces unless the task says to — if you have to, call it out. ### 3. Implement Edit only the files the task needs. For multi-part tasks, work in small steps that each run. Handle the important ways the code can fail. ### 4. Test and verify Add or update tests when behavior changes, a bug is fixed, an interface changes, or a real edge case is introduced. Run the tests for the change, any checks the task requested, then the project's wider checks — including the full test suite if you can. Check the acceptance criteria. Fix what the checks catch without going beyond the task. ### 5. Review Review the final diff, using a review sub-agent for non-trivial changes when available. Check for bugs, missing or weak tests, broken contracts, unrelated changes, important risks, and whether the change satisfies the task's acceptance criteria. Make sure tests prove the changed behavior instead of only exercising code. Fix valid findings while staying within scope, then rerun the relevant checks. ### 6. Report Say what changed. List the tests and checks you ran, including requested checks. Report acceptance criteria status. Mention review findings or fixes. Call out anything important you couldn't verify. If the task came from an issue tracker, mark it ready for review. ## Rules - One task at a time. - Don't bundle separate changes together if they could be separate steps. - If an assumption is low-risk, say what it is and keep going. - Don't hide what you couldn't verify. - Don't use the task as an excuse to clean up unrelated code.
Related in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.