メニュー
Post-verify PR flow - creates a clean PR branch, invokes code review check, and prepares the PR for merge. Activates for requests involving finishing a cycle, packaging design output, or moving work to a pull request.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hegemonart/get-design-done --skill gdd-shipコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Master design pipeline for Claude Code. 5-stage workflow: Brief → Explore → Plan → Design → Verify. Run 'brief' first in any new project to capture the design problem, then 'explore' to inventory the codebase and interview for context. Invoke without arguments for status and auto-routing.
Run the pipeline with optional agents skipped for speed. Skips: phase-researcher, design-assumptions-analyzer, design-integration-checker. Keeps: planner, executor, verifier, auditor. Activates for requests involving a lightweight design pass, a fast iteration, or a quick low-ceremony change.
Routes a /gdd command to fast|quick|full path + S|M|L|XL complexity_class and returns {path, complexity_class, model_tier_overrides, resolved_models, estimated_cost_usd, cache_hits}. A SKILL.md prompt the model executes to emit a routing-decision JSON from rule tables (no separate agent spawn). Optional/advisory - invoked only by the skills that opt into routing; the budget-enforcer hook tolerates its absence. Read by hooks/budget-enforcer.ts.
SOC 職業分類に基づく
SKILL.md を表示中
| name | gdd-ship |
| description | Post-verify PR flow - creates a clean PR branch, invokes code review check, and prepares the PR for merge. Activates for requests involving finishing a cycle, packaging design output, or moving work to a pull request. |
| argument-hint | [--title <PR title>] [--draft] |
| tools | Read, Write, Bash, AskUserQuestion, Task |
| disable-model-invocation | true |
Closes the verify → merge gap: runs {{command_prefix}}pr-branch for a clean branch, assembles a PR body from design artifacts, and creates the PR via gh.
.design/DESIGN-VERIFICATION.md exists and shows a pass. If missing or failing, ask: "Verify has not completed / failed. Ship anyway? (yes/no)"{{command_prefix}}pr-branch to produce a branch with only src/ commits (no .design/ or .planning/ noise). Use the resulting branch for the PR.--title argument if given, otherwise ask (AskUserQuestion): "PR title?".design/DESIGN-PLAN.md.design/DESIGN-VERIFICATION.md (per-task pass/fail).design/DESIGN-AUDIT.md if present
Format as Markdown with ## Goals, ## Verification, ## Audit sections.gh pr create --title "<title>" --body "<body>" [--draft] via Bash. If gh is not installed, print the full body and instruct the user to create the PR manually.main/master directly..design/ or .planning/ files in the PR branch - that is {{command_prefix}}pr-branch's job.ONLY on the success path - after the PR has been created (Step 5) and its URL printed (Step 6) - spawn agents/pr-commenter.md via the Task tool to post GDD's verify/audit output inline on the new PR: inline review comments on changed lines, Preview/Chromatic before-after screenshot pairs, and the gdd/design-review check-run (audit pillar scores + verify pass/fail + a11y). Pass the PR number + owner/repo in the Task context.
This is a degrade-to-noop surface and MUST NOT fail the ship: if gh is unavailable, the GDD_DISABLE_PR_COMMENTER kill-switch (env or .design/config.json) is set, or the agent errors, the ship still succeeds (pr-commenter prints the bodies for manual paste). Skip this step entirely if PR creation failed in Step 5. The posting contract (gh-api shapes, check-run payload, redaction, branch-protection setup) lives in reference/pr-review-integration.md.
ONLY on the success path - after the PR has been created and the URL has been printed - emit the plugin-update banner. If PR creation failed earlier, skip this step (do not suggest upgrades in the middle of a PR-creation failure).
[ -f .design/update-available.md ] && cat .design/update-available.md
Written by hooks/update-check.sh; suppressed mid-pipeline and when the latest release is dismissed.