メニュー
Produce a concrete coding plan from a Jira ticket or a plain description: file locations, implementation steps, and edge cases. Use when: planning work, breaking down implementation, figuring out where to start coding.
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 | plan-work |
| description | Produce a concrete coding plan from a Jira ticket or a plain description: file locations, implementation steps, and edge cases. Use when: planning work, breaking down implementation, figuring out where to start coding. |
| argument-hint | Jira ticket key (e.g. DT-1234) or a description of the work |
Produce a concrete, actionable coding plan from a ticket or a plain description of the work.
If a Jira ticket is available, follow the jira-read-ticket skill to fetch and summarize it.
Otherwise, use the user's description of the work. If it's too vague to plan from, ask a clarifying question. Write a brief summary of the goal before continuing.
Search the codebase to understand where the change lives:
Output a numbered implementation plan. Each step should be:
Example format:
1. Edit `src/checkout/DiscountField.tsx` — add controlled input for discount code
2. Update `src/checkout/checkoutSlice.ts` — add `discountCode` to state and a `setDiscountCode` action
3. Edit `src/api/checkout.ts` — pass `discountCode` in the order payload
4. Add `src/checkout/DiscountField.test.tsx` — unit tests for input validation
List any: