implement

name	implement
description	Implement a given improvement or bug ticket's implementation plan, previously generated by either the 'brainstorm' or 'troubleshoot' commands. This command will execute the implementation plan, making the necessary changes to the codebase, configuration, or infrastructure as specified in the plan.
argument-hint	Please provide the GitHub Issue id for the improvement or bug ticket you would like to implement.
disable-model-invocation	true

This skill is designed to help users implement a given improvement or bug ticket's implementation plan, previously generated by either the 'brainstorm' or 'troubleshoot' commands. It takes into account the context, requirements, and constraints provided in the ticket or request, and executes the implementation plan by making the necessary changes to the codebase, configuration, or infrastructure as specified in the plan.

Workflow

Step 1 — Parse the Request

Verify if the provided input refers to an open GitHub Issue by utilizing the GitHub MCP.

If it doesn't match a valid GitHub Issue, or the GitHub Issue does not contain an implementation plan, inform the user to use the brainstorm or troubleshoot skills to generate an implementation plan for the issue first, and end the conversation here.

Step 2 — Execute Implementation Plan

With the implementation plan and any relevant context gathered from the GitHub Issue, execute the implementation plan by making the necessary changes to the codebase, configuration, or infrastructure as specified in the plan as follows:

• check if the codebase is up-to-date with the latest changes from the main branch, and if not, pull the latest changes and try to resolve any merge conflicts. if not possible, inform the user to resolve the conflicts manually and end the conversation here.

• check if we have a local branch for the GitHub Issue (following the naming convention: feature/gh-{GITHUB_ISSUE_ID}), and if not, create a new branch for the issue locally

• apply the changes specified in the implementation plan to the codebase, configuration, or infrastructure, following best practices for code quality, security, and maintainability. If the codebase contains an AGENTS.md file, or any *.instructions.md file, parse it to extract any explicit instructions or constraints that may affect the implementation. Those instructions should be treated as authoritative and incorporated into the implementation process with higher priority. They overrule any implicit assumptions you might make about the codebase.

• check for missing tests, documentation, or other artifacts that are required by the implementation plan, and create them as needed (use the write-tests skill if available). If the implementation plan specifies any new dependencies or configuration changes, ensure that they are properly documented and integrated into the codebase.

• make sure to run any necessary tests, linters, or build processes to ensure that the changes are valid and do not introduce new issues. If any issues are detected, fix them before proceeding. For integration tests you may need to set up specific test environments or mock services (refer to the run-tests skill for guidance if available).

• commit the changes to the local branch, push the branch to the remote repository, and create a GitHub Pull Request for review (use create-pr skill if available). Include a clear description of the changes made, referencing the GitHub Issue id and any relevant context.

Step 3 — Code Review

Finally, run a thorough code review via the code-review skill for the new branch and publish the review results to the GitHub Pull Request.