菜单
Promote a task artifact pack into a canonical spec under /docs/specs or /docs/architecture/specs, following /docs/spec-guide.md lifecycle (active-only, delete replaced). No writes without APPROVE.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | canon-spec-publishing |
| description | Promote a task artifact pack into a canonical spec under /docs/specs or /docs/architecture/specs, following /docs/spec-guide.md lifecycle (active-only, delete replaced). No writes without APPROVE. |
Turn stable knowledge from WORK_PATH into a canonical spec in /docs/**.
/docs/specs/ or /docs/architecture/specs//docs/spec-guide.md if present and follow it as the single source of truth.
If absent: apply default conventions (self-contained canonical spec, active-only,
delete replaced specs, rely on git history for old versions)./docs/** (delete replaced specs, rely on git history).Grounding:
/docs/spec-guide.md if present/docs/**/specs/README.md index if presentDecide publish target:
NNN-short-title.md in the correct folder.
Compute NNN:
NNN-*.md files in the target folder.001.Compose canonical spec:
Coherence gate:
/docs/**Return control to Fabricator.
Use after git-tooling push to create or manage a PR on Bitbucket Server. Composes PR description, creates PR via API, handles review comments. Terminal delivery step. (5 supporting files)
Use at session start to pull Jira issue details into context, or post-delivery to create/update issues. Integrates with task-authoring (issue → task.md) and git-tooling (commit links). (2 supporting files)
Select the minimal sufficient artifact set (task/requirements/tech-spec/contracts/models/verify/evidence) for the current change, and recommend the next skills. Use after task intake or when scope/risk changes.
Define interface/persistence contracts (APIs, schemas, deeplinks, storage formats) + compatibility rules. Use when public surfaces or stable formats are involved.
Implement changes guided by existing artifacts and repo conventions (AGENTS/README/DEVELOPMENT + WORK_PATH). Make small diffs, follow coherence gate, and optionally trigger verification-run.
Model states/flows/invariants for complex behavior (async, retries, caching, offline). Use when correctness depends on state machines or non-trivial flows.