Plan
claim-issue
Claim a spec'd issue by creating its feature branch, a placeholder plan, and a draft pull request.
What it does
claim-issue sets up the working surface for an issue you're about to build. In one step it:
- Assigns the issue to you and marks it as claimed.
- Creates the feature branch for the work.
- Writes a placeholder implementation plan you'll fill in next.
- Opens a draft pull request linked to the issue.
When it finishes, the issue has a home: a branch to commit to and a draft PR that tracks progress from now through review.
When to use it
Reach for claim-issue once an issue is spec'd and you're ready to start on it, right after /cl-dev:spec has produced a clear issue with acceptance criteria, and before you plan the implementation.
It's the entry point to hands-on work in the workflow:
spec → claim-issue → create-impl-plan → implement → review → mergeClaiming first means the branch and draft PR already exist when you move on to /cl-dev:create-impl-plan, so your plan and every commit have somewhere to land.
How to invoke it
From your coding agent, in the repository where the work lives:
/cl-dev:claim-issueTell it which issue you're claiming (the issue's ID or number) if it isn't already clear from your conversation.
Before you run it, make sure:
- The issue is spec'd (run
/cl-dev:specfirst if it isn't). - You've set up the repository with
/cl-dev:initand your CodeLantern account is connected to it.
Plan
Related skills
Other skills in the same phase of the workflow.
| approve-plan | Approve a drafted implementation plan so implementation can begin. |
| create-impl-plan | Turn a claimed issue into a phased implementation plan an agent can execute. |
| design-solution | Shape and pressure-test a solution design for a larger issue before you commit to a plan. |
| grill | Pressure-test a spec, design, or idea to surface hidden assumptions, open questions, and fuzzy language before they cost you. |
| reduce-complexity | Run an interactive complexity review of a design, plan, or code to find the parts carrying too much weight and simplify them. |
| review-design | Get a written structural, security, and privacy review of a design or plan before you build. |
| spec | Turn a plain request into a detailed specification captured as a project issue with testable acceptance criteria. |