From buyoung-skills
Executes code tasks from Linear sub-issues: resolves dependencies, implements changes, validates Done Criteria, and syncs status. Use for working on Linear issues like PRI-42.
npx claudepluginhub buyoung/skills --plugin backend-skillsThis skill uses the workspace's default tool permissions.
Execute code tasks from Linear issues produced by the `linear-issue-creator` skill.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Execute code tasks from Linear issues produced by the linear-issue-creator skill.
Read structured sub-issues, resolve dependency order, perform the actual file changes,
and keep Linear in sync throughout.
The creator produces a 1 main issue + N sub-issues structure. Each sub-issue contains everything needed for one unit of code work: Task Description, Target Location, Technical Details, Done Criteria, and Dependencies. This skill consumes that structure and turns it into real code changes.
The user provides a main issue identifier (e.g., PRI-42).
Linear:get_issue with includeRelations: trueLinear:list_issues with parentId set to the main issue identifierLinear:get_issue with includeRelations: true to retrieve blockedBy data
get_issue fails for a sub-issue, retry once. If it still fails, use the data already available from list_issues and check the blocks field of other sub-issues to infer the dependency graphDone or CanceledblockedBy entries, or all its blockers are DonePresent the execution plan and wait for user confirmation:
📋 Execution Plan for PRI-42:
1. PRI-43 — [project] Configure hotkey plugin (no dependencies)
2. PRI-44 — [project] Build settings UI (blocked by PRI-43)
Proceed?
For each sub-issue in order, run the full execution cycle below. After completing one sub-issue, re-evaluate the remaining list — previously blocked issues may now be ready.
Parse each section of the sub-issue description:
| Section | How to use it |
|---|---|
| Task Description | Understand what to build / change / fix |
| Target Location | Open these files to understand current code structure |
| Technical Details | Plan the implementation — patterns, libraries, API specs |
| Done Criteria | Exit conditions — every item must be satisfiable |
| Dependencies | Verify prerequisite sub-issues are already Done |
Check the sub-issue's labels to determine approach:
| Label | Approach |
|---|---|
Front-end | Work in frontend codebase, verify from browser/UI perspective |
Back-end | Work in server codebase, verify from API/DB perspective |
Feature | Design-first, build the new thing |
Bug | Root-cause analysis first, then fix |
Refactor | Preserve behavior, improve structure |
Chore | Config / build / dependency changes |
Perf | Measure before and after |
Docs | Documentation changes only |
Update the issue status:
Linear:save_issue
id: "<sub-issue-id>"
state: "started"
Post a start comment (write in Korean, Professional tone, no AI patterns — natural and direct):
Linear:save_comment
issueId: "<sub-issue-id>"
body: |
## 🚀 Work Started
### Approach
- [Implementation approach summary — include specific technical decisions]
- [Key files to modify or create]
- [Notable decisions or trade-offs]
Guidelines:
package.json / requirements.txt or equivalent first. Install if reasonable, or note the gapBefore marking complete, go through each Done Criteria checkbox:
Linear:save_comment
issueId: "<sub-issue-id>"
body: |
## ✅ Work Complete
### Changes
- `path/to/file1.ts` — [what changed]
- `path/to/file2.ts` — [new file, what it does]
### Done Criteria
- [x] Criterion 1 — [brief evidence]
- [x] Criterion 2 — [brief evidence]
### Notes
- [Any deviations, edge cases discovered, etc.]
Comment Quality Guide (Content Skill Principles):
Apply these principles when writing completion comments to improve quality. Target audience: Fullstack developers | Language: Korean | Tone: Professional
Linear:save_issue
id: "<sub-issue-id>"
state: "Done"
Re-evaluate the remaining sub-issues. Issues that were blocked by the just-completed one may now be ready. Pick the next ready sub-issue and repeat from 3a.
For exception handling (missing files, unavailable dependencies, ambiguous criteria, blockers, deadlocks), see references/exceptions.md.
When all sub-issues are processed:
Linear:save_comment
issueId: "<main-issue-id>"
body: |
## 📋 Overall Completion Report
### Completed Sub-Issues
- [x] SUB-01 — Title
- [x] SUB-02 — Title
### Incomplete Sub-Issues (if any)
- [ ] SUB-03 — Title (reason: ...)
### Acceptance Criteria Review
- [x] Criterion from main issue — satisfied by SUB-01, SUB-02
- [ ] Criterion from main issue — not yet met (reason: ...)
### Summary
[Concretely summarize all changes and current state]
For Linear API details (state values, description parsing, tool calls, retry policy), see references/linear-api.md.