From skill-issue
Converts a plan of record into Linear issues with dependencies, acceptance criteria, and sequencing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skill-issue:linear-issue-shapingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Convert a plan of record into well-shaped Linear issues with the right granularity, sequencing, and acceptance criteria. Issues should be independently workable and traceable back to the plan.
Convert a plan of record into well-shaped Linear issues with the right granularity, sequencing, and acceptance criteria. Issues should be independently workable and traceable back to the plan.
Linear provides these organizational levels. Use what fits the work.
--description-file for all descriptions.Each issue description follows this structure.
Plan Reference: Include the ## Plan Reference section only when there is a plan file in this repository with an actual path you can link (e.g. docs/foo-plan.md). If the plan lives only outside the repo (Linear doc, Notion, chat, no checked-in plan), omit the entire Plan Reference section—no section header, no bullets, no placeholders.
When a repo-linked plan exists, insert Plan Reference immediately after Problem, using this shape:
## Plan Reference
- Plan: `<path to plan file in this repository>`
- Phase/Component: `<which part of the plan this implements>`
- Spec Sections: `<relevant spec sections, if applicable>`
- Reference Implementation: `<path to reference code, if applicable>`
Full template (Problem through Architecture Notes; insert the Plan Reference block from above only when applicable):
## Problem
What this issue solves or implements. One paragraph.
## Scope
What is included in this issue.
## Non-Goals
What is explicitly excluded from this issue.
## Acceptance Criteria
- [ ] <criterion from the plan>
- [ ] <criterion from the plan>
## Verification
How to prove the work is correct.
## Architecture Notes
Relevant design context from the plan. Package, types, API surface.
linear initiative create \
--name "<initiative name>" \
--description "<description with implementation details>" \
--status planned
linear initiative add-project <initiative-id-or-name> <project-slug>
linear milestone create \
--project "<project slug>" \
--name "<milestone name>"
cat > /tmp/issue-desc.md <<'EOF'
<issue description from template>
EOF
linear issue create \
--title "<issue title>" \
--description-file /tmp/issue-desc.md \
--project "<project slug>" \
--milestone "<milestone name>" \
--priority <1-4> \
--state "Todo" \
--no-interactive
After all issues are created:
linear issue relation add <issue-id> blocked-by <blocking-issue-id>
--description-file for all issue descriptions. Never pass markdown inline.npx claudepluginhub crown-dev-studios/skill-issue --plugin skill-issueGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.