菜单
Kick off a new feature — stress-test the plan with grill-with-docs, break it into tickets with to-issues, then commit any doc changes to develop. Use when you have a feature idea or rough plan and want to go from concept to a clean set of GitHub issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pick up a GitHub issue by number and drive it from clarification through implementation, PR, a single automated review pass, and fixing the resulting remarks. Use when the user gives a bare ticket/issue number and asks to implement, pick up, or ship it (e.g. "/implement-ticket 123", "pick up ticket 123", "implement issue
Run a design-review session on an existing page — create the branch, invoke frontend-design, build incrementally with screenshots, then PR into develop. Use when visually overhauling an existing page or section.
Run the post-merge checklist after a feature PR lands on develop — pull latest, add awaiting-promotion label to the issue, update CLAUDE.md/CONTEXT.md if stale, and commit docs directly to develop. Use when a feature PR has just merged into develop and you want to run the standard follow-up steps.
Promote develop to main — apply any pending migrations, open the develop→main PR with Closes
| name | plan-feature |
| description | Kick off a new feature — stress-test the plan with grill-with-docs, break it into tickets with to-issues, then commit any doc changes to develop. Use when you have a feature idea or rough plan and want to go from concept to a clean set of GitHub issues. |
| disable-model-invocation | true |
Sequences the full feature planning workflow. Three steps, in order.
Invoke the grill-with-docs skill. Let it run to completion — this is an interactive session that sharpens the plan against the existing domain model and updates project documentation inline as decisions crystallise. Do not move to step 2 until the session concludes and the user is happy with the outcome.
Invoke the to-issues skill to turn the crystallised plan into independently-grabbable GitHub issues. Do not hand-roll gh issue create calls — to-issues knows how to slice a plan into tracer-bullet vertical slices.
After the issues are created, check for uncommitted changes to any project documentation files (e.g. CONTEXT.md, docs/adr/, CLAUDE.md, or equivalent):
git status
If there are changes, commit and push them directly to develop — no branch or PR needed for doc-only updates:
git checkout develop && git pull
git add <changed doc files>
git commit -m "docs: update documentation after planning session"
git push
If nothing changed, skip this step.
/ship-ticket).Closes #N in any commits here — that belongs in the develop → main promotion PR.