메뉴
Start work on a new task: read a Jira ticket, create a git worktree with a properly named branch, produce a coding plan, and move the ticket to In Progress. Use when: starting a new task, picking up a ticket, beginning a feature, start work, new worktree.
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 | start-work |
| description | Start work on a new task: read a Jira ticket, create a git worktree with a properly named branch, produce a coding plan, and move the ticket to In Progress. Use when: starting a new task, picking up a ticket, beginning a feature, start work, new worktree. |
| argument-hint | Optional: Jira ticket number (e.g. DT-1234) |
Full workflow to go from a ticket (or description) to a ready-to-code workspace with a plan.
If a Jira ticket was provided (or can be inferred from context):
jira-read-ticket skilljira-transition skill targeting "In Progress" — this also assigns the ticket to you if it's unassignedadd-discount-code-checkout)If no ticket, ask: "What are you working on? (brief description for the branch name)" and derive the slug from the answer.
Check whether Claude is already running inside a linked worktree:
git rev-parse --git-dir
git rev-parse --git-common-dir
If the two outputs differ, you are already in a linked worktree — skip to Step 3.
If they are the same (main checkout), follow the create-worktree skill, passing the ticket key (if any) and the derived slug as context for the branch name.
Follow the plan-work skill using the ticket (or the user's description) fetched in Step 1.
Present the coding plan. If a new worktree was created in Step 2, also share the worktree path. If already in a worktree, just confirm the branch and present the plan.