impl-implement
Scannednpx machina-cli add skill bryanp/agent-skills/implement --openclawImplement a specific step of an implementation plan from the given Linear issue.
Rule: Identity
First use the identity skill to assume the identity of the agent.
Rule: Find Plan
You might be given the top-level plan or a specific step. You can differentiate by checking if the issue is an epic (contains sub-issues) or is standlone. Step issues are standalone, while top-level plans are epics.
When the next step to implement is ambiguous, scan all steps in the plan and pick the very next unimplemented step. If you still aren't sure what to do, ask the user for clarification.
Get information about the plan step issue using the linear-issue-view skill.
Rule: Issue Status
Change the issue status to "In Progress" when starting work on the issue. Ensure the parent issue also has a status of "In Progress".
Once the work is committed, change the status to "In Review". Assign yourself when starting. If this is the last step of the plan, update the parent issue to "In Review".
Use the linear-issue-update skill to make changes to the issue.
Rule: Commit Work
Use the git-branch skill to work from a new branch. Name the branch with the Linear
issue id. Use the git-commit skill to commit your work after proving it works.
Rule: Show Proof
Use the prove skill to capture proof that the plan step is correct.
Rule: Request Feedback
Once verified, use the github-pr-open skill to open a new pull request. The body
of the pull request should contain the proof you generated above.
Source
git clone https://github.com/bryanp/agent-skills/blob/main/code/impl/implement/SKILL.mdView on GitHub Overview
Impl-implement executes a defined step of an implementation plan. It identifies the next unimplemented step, updates statuses to In Progress, and then proceeds through branching, committing, proving, and PR creation.
How This Skill Works
The skill assumes identity, fetches plan details with linear-issue-view to locate the next unimplemented step, and updates the issue and its parent to In Progress. It then creates a branch named after the Linear issue id (git-branch), commits verified changes (git-commit), captures proof (prove), and opens a PR with the proof (github-pr-open).
When to Use It
- You need to implement the next unstarted step in a Linear plan.
- Starting work requires updating the step and parent plan to In Progress.
- You must commit and prove that the step works before signaling completion.
- The step is ready for code review and you need to open a PR with proof.
- If there is ambiguity about which step comes next, you should request clarification.
Quick Start
- Step 1: Identity - assume agent identity.
- Step 2: Inspect plan with linear-issue-view to find the next unimplemented step.
- Step 3: Create a branch (git-branch), implement, prove, commit (git-commit), and open PR (github-pr-open).
Best Practices
- Always verify the next unimplemented step with linear-issue-view before acting.
- Set the issue and its parent to In Progress before coding begins.
- Name the git branch after the Linear issue id for traceability.
- Use prove to capture verifiable proof and include it in the PR body.
- If the step completes, update the parent to In Review and open a PR with github-pr-open.
Example Use Cases
- Implementing the 'Create User Endpoint' step in a user-auth plan and moving the parent to In Progress.
- Starting work on a step, updating statuses, and branching for changes using the Linear issue id.
- Committing code only after proving the step works, then documenting proof for review.
- Opening a PR with the proof content once the step passes verification.
- Clarifying the next step when multiple steps appear unimplemented.
