From Vengineer
Decompose one or more plan files into actionable GitHub issues — one issue per concrete implementation task (~1-4h of work) with title, body, labels, and effort estimate.
npx claudepluginhub dylanliiii/shipyard --plugin VengineerThis skill is limited to using the following tools:
**Purpose**: Read one or more plan files and decompose them into a set of small, actionable GitHub issues. Each issue maps to a single concrete implementation task estimated at 1-4 hours of work.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Purpose: Read one or more plan files and decompose them into a set of small, actionable GitHub issues. Each issue maps to a single concrete implementation task estimated at 1-4 hours of work.
${ARGUMENTS} — optional path(s) to plan file(s). If omitted, the skill lists available plans and lets the user choose.
Verify gh is available and authenticated:
gh auth status
If not authenticated, print:
ghCLI is not authenticated. Rungh auth loginand try again. Then stop.
Identify the current GitHub repo context:
gh repo view --json name,owner,defaultBranchRef
${ARGUMENTS} contains file paths, use those directly.docs/plans/:
ls docs/plans/
docs/plans/ is empty or absent, ask the user to paste or describe the plan content directly.For each selected plan file, spawn a Task (general) agent with the following prompt:
You are an issue decomposition analyst. Read the plan at <path> and produce a JSON array of actionable GitHub issues.
Rules:
- One issue per concrete implementation task (roughly 1-4 hours of work).
- Tasks that are larger than 4h MUST be split further.
- Group tasks into logical work packages: backend, frontend, infra, test, docs, chore.
- Preserve traceability — reference the originating plan section in each issue body.
For each issue output:
{
"title": "<conventional-commit-style title, e.g. feat: add OAuth callback endpoint>",
"work_package": "<backend|frontend|infra|test|docs|chore>",
"effort": "<S|M|L>", // S = <2h, M = 2-4h, L = >4h (flag, should be split)
"body": "<markdown body — see body template below>",
"labels": ["<type>", "effort:<S|M|L>"],
"milestone": "<inferred from plan filename or section, or null>"
}
Body template:
## Overview
<1-2 sentence description of the task>
## Acceptance Criteria
- [ ] <specific, testable criterion>
- [ ] ...
## Context
<relevant background, references to plan sections, file paths, or related issues>
Collect all agent outputs and merge into a single flat issue list.
Display the full list in a readable table:
# | Work Package | Effort | Title
---|--------------|--------|-------
1 | backend | M | feat: add OAuth callback endpoint
2 | backend | S | chore: add env var for OAuth client secret
...
Flag any effort: L items with a warning:
⚠ Issue #N has effort L — consider splitting it before creating.
Use AskUserQuestion to ask:
"Here are the N issues I've derived from the plan(s). How would you like to proceed?"
Options:
Before creating issues:
Fetch existing labels:
gh label list --json name --jq '.[].name'
For each required label not yet present, create it:
gh label create "<label>" --color "<auto-pick color>" --description "<description>"
Use these default colors:
| Label | Color |
|---|---|
| enhancement | #a2eeef |
| bug | #d73a4a |
| chore | #e4e669 |
| test | #0075ca |
| docs | #cfd3d7 |
| effort:S | #c2e0c6 |
| effort:M | #fef2c0 |
| effort:L | #f9d0c4 |
If a milestone was inferred, check whether it exists:
gh milestone list --json title --jq '.[].title'
If not, create it:
gh milestone create --title "<milestone>" --description "Auto-created by batch-issues skill"
For each issue in the approved list:
gh issue create \
--title "<title>" \
--body "<body>" \
--label "<label1>" --label "<label2>" \
[--milestone "<milestone>"]
Print progress as each issue is created:
✓ Created #42 — feat: add OAuth callback endpoint
✓ Created #43 — chore: add env var for OAuth client secret
...
Print a summary table linking each created issue:
Created N issues:
#42 [M] feat: add OAuth callback endpoint → https://github.com/...
#43 [S] chore: add env var for OAuth client secret → https://github.com/...
Use AskUserQuestion to present options:
"All N issues created. What next?"
Options:
gh issue list --web/core:work — begin implementing the first issue| Situation | Action |
|---|---|
gh not installed | Print install instructions: brew install gh |
| Not authenticated | Print gh auth login and stop |
| No remote GitHub repo | Print gh repo create suggestion and stop |
| Plan file not found | Ask user to verify path or paste content directly |
| Issue creation fails | Print the error, skip that issue, continue with the rest, list failures at end |
gh issue list --search "<title>") before confirming creation