メニュー
Break a large initiative into sequenced, independently-shippable tickets and milestones. Use when: decomposing an epic, breaking down a large project, planning a multi-ticket initiative, sequencing work across milestones.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.
Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.
Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.
Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.
Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.
Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.
| name | decompose-epic |
| description | Break a large initiative into sequenced, independently-shippable tickets and milestones. Use when: decomposing an epic, breaking down a large project, planning a multi-ticket initiative, sequencing work across milestones. |
| argument-hint | An initiative description or a parent Jira ticket key (e.g. DT-1234) |
Turn a large initiative into a sequenced set of discrete, independently-shippable tickets. This is the altitude above plan-work — it produces the tickets; plan-work/start-work then plan each one.
jira-read-ticket skill to pull its intent and scope.State the initiative's goal and what "done" looks like in one paragraph.
Explore the codebase enough to ground the breakdown in reality. Then:
Break each workstream into tickets that are independently shippable and small enough to fit a few days. For each:
- <Proposed title>
Scope: one-line description of what it delivers.
Size: S / M / L (rough).
Depends on: <other ticket(s)>, or "none".
Prefer vertical slices that deliver value over horizontal layers that don't ship alone.
Order the tickets into milestones along the critical path. Output:
Ticket creation in Jira is out of scope — this produces the plan. Mention creating the tickets as the manual follow-up.