From buyoung-skills
Creates structured Linear issues (1 main + N sub-issues) with project linking, title prefixes, and labels for back-end/front-end tasks. Supports generic code workflows or PRD pipeline with Korean descriptions for fullstack devs. Use for creating or breaking down tasks.
npx claudepluginhub buyoung/skills --plugin backend-skillsThis skill uses the workspace's default tool permissions.
Create issues in Linear using the Linear MCP with a **1 main issue + N sub-issues** structure.
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.
Create issues in Linear using the Linear MCP with a 1 main issue + N sub-issues structure.
| Aspect | Main Issue | Sub-Issue |
|---|---|---|
| Perspective | Business / user perspective | Developer / engineer perspective |
| Unit | One feature or problem | One PR-completable task |
| Key question | "What changes for the user?" | "What code do we change?" |
| Labels | None | Exactly 2 (1 area + 1 type) |
| Status mgmt | Auto-completes when all sub-issues are done | Transitions individually |
Before gathering requirements, determine the workflow type:
| Workflow | When to use | Description |
|---|---|---|
| Generic | Code tasks: feature, bug, refactor, etc. | Use existing flow as-is |
| PRD Pipeline | Issues requiring a PRD (product requirements doc) or feature spec | Apply content skill principles for high-quality descriptions |
If the user doesn't specify, infer from the work description. Ask if unclear.
Every issue (main + sub) must be linked to a project via the project parameter.
Every issue title must start with [ProjectName].
Examples:
[corral] Implement global hotkey system[corral] Configure Tauri global hotkey pluginEach sub-issue must have exactly 2 labels. The main issue has no labels.
Area label (pick exactly 1):
Back-endFront-endType label (pick exactly 1):
Bug — Bug fixChore — Build, config, dependency maintenanceDocs — DocumentationPerf — Performance improvementRefactor — Code refactoring (no behavior change)Feature — New feature or feature updateAlways use "private" as the team when creating issues.
Confirm the following with the user:
If the user has already provided sufficient information, proceed directly. Otherwise, ask.
Call Linear:save_issue to create the main issue.
Parameters:
title: "[ProjectName] Main title"
team: "private"
project: "project-name"
description: (use template below)
priority: appropriate priority (1=Urgent, 2=High, 3=Normal, 4=Low)
Use the main issue description template from references/templates.md.
Do NOT assign any labels to the main issue.
Use the main issue's ID as parentId for each sub-issue.
Parameters:
title: "[ProjectName] Sub-task title"
team: "private"
project: "project-name"
parentId: "main issue ID or identifier"
labels: ["area-label", "type-label"] ← always exactly 2
description: (use template below)
priority: appropriate priority
Use the sub-issue description template from references/templates.md.
If sub-issues depend on each other, connect them with blockedBy.
Linear:save_issue (update)
id: "dependent issue identifier"
blockedBy: ["prerequisite issue identifier"]
Summarize all created issues for the user:
For a full flow example, see references/templates.md.
Workflow for producing PRD-quality (product requirements document) issue descriptions. Applies principles from four content skills (content-strategy, content-production, content-humanizer, copy-editing) during the description writing process.
Fixed context:
Collect the same information as Generic Step 1 (Project, Work description, Area, Type). Additionally confirm:
| Pattern | Starting state | Content skill stages to apply |
|---|---|---|
| A. Blank → Complete | Topic only | content-strategy → content-production → content-humanizer → copy-editing |
| B. Draft → Complete | Draft exists | content-humanizer → copy-editing |
| C. Polish only | Nearly complete | copy-editing |
Apply the applicable stages in order to write issue descriptions.
See references/prd-pipeline.md for the detailed guide.
Pattern A (Blank → Complete) — All 4 stages:
content-strategy principles: Plan the PRD structure
content-production principles: Draft the descriptions
content-humanizer principles: Remove AI patterns
copy-editing principles: Run PRD-relevant Seven Sweeps checks
Pattern B (Draft → Complete): Apply stages 3-4 only Pattern C (Polish only): Apply stage 4 only
Same as Generic Step 2 — call Linear:save_issue.
Use the PRD Main Issue Description Template from references/templates.md.
Same as Generic Step 3 — create sub-issues.
Use the PRD Sub-Issue Description Template from references/templates.md.
Same as Generic Steps 4-5.
Verify before creating any issue:
Common:
[ProjectName]?parentId point to the main issue?project?PRD Pipeline additional checks (when PRD workflow is selected):