菜单
Produce a production hotfix — branch from main, fix, change-review back into main, then merge the fix back into develop. Use when a bug in the released version (main) must be patched without waiting for the normal develop→main cycle.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add a new project-specific agent mid-project, with Chief AI Officer drafting the definition and justification, and the user approving. Use when project scope expands (new domain emerges, a parallel track is needed, or critical expertise is missing) during Phase 2.
Add a new MCP server to the project mid-project. Wraps the capability-management procedure — external MCP search, ADR draft, .mcp.json update, user install instructions, and capability-log entry. User approval is mandatory regardless of involvement level. Use when an authorized agent identifies a missing external integration.
Add a new project-specific skill mid-project. Wraps the capability-extension procedure — reuse audit, skill-creator invocation, capability-log entry, user approval, and reload reminder. Use when an authorized agent identifies a missing helper-skill capability during Phase 1 STEP 2/3 or anywhere in Phase 2.
Re-activate a Phase 1 agent from STANDBY because a requirement, design, roadmap, team-composition, or documentation drift has been detected. The user invokes this with the target agent name and a brief reason. Use when Phase 2 cannot proceed without a Phase 1 decision.
Initialize a new project with a structured, multi-agent workflow — discovery interview, operating preferences, technical design, agent team formation, roadmap construction, documentation consolidation, and a final user approval gate. Use when the user starts a fresh project and wants a rigorous setup before any code is written.
Render the active milestone's tasks as a kanban board grouped by lane (backlog / todo / in-progress / in-review / done). Forge-aware — GitHub mode shows the Projects v2 URL alongside ASCII fallback; other forges render ASCII only. WIP overflow is flagged but not blocked. Use whenever the user asks "what's where" or wants a quick board view.
| name | hotfix |
| description | Produce a production hotfix — branch from main, fix, change-review back into main, then merge the fix back into develop. Use when a bug in the released version (main) must be patched without waiting for the normal develop→main cycle. |
You are the Conductor coordinating a production-path fix that bypasses the normal develop cycle.
main (released) that cannot wait for the next milestone release.Not for: ordinary bugs found in develop — use the normal task cycle.
docs/roadmap/tasks/h<NN>-<slug>.md.git checkout main && git pull
git checkout -b fix/h<NN>-<kebab-slug>
Open change request against main. All three reviewers still required, but reviewers acknowledge expedited status and aim for same-day turnaround:
Unanimous approval required (no relaxation to majority for hotfixes).
atelier-check-reviews <CR-NUMBER> --policy unanimous
<forge> merge --delete-source-branch
git checkout main && git pull
git tag vX.Y.<Z+1> # patch version bump
git push origin vX.Y.<Z+1>
git checkout develop && git pull
git merge main # or cherry-pick if divergence is large
# resolve conflicts, prefer develop's version for non-hotfix code
git push origin develop
If the back-merge conflicts materially with in-flight develop work, escalate to Tech Lead for resolution before push.
docs/roadmap/lessons-learned.md.docs/roadmap/postmortems/pm-<NN>-<slug>.md.main without also planning the back-merge to develop.develop directly — that's a regular task, not a hotfix.docs/process/change-review-workflow.md (expedited variant of the normal cycle)docs/process/git-flow.md (hotfix branch pattern)docs/process/release-process.md