Menu
Check, acquire, or release a governed scope lock.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
ATM Captain 派工治理。觸發詞 派工 / 派工單 / dispatch / 開卡 / 派任務 / 派代理 / Phase 0 / Phase 1 / AAO / task card / condition review / 收口。負責 AI-Atomic-Framework (AAF) + 3KLife 雙 repo 治理：強制 Context Map 4 層、雙代理拆分（防外卡 mirror commit）、AAF 嚴格 2 commit、3KLife target_repo 嚴格 1 commit、7-8 段回報、禁止清單前置強化、Captain condition review。承載 0064 → 0093+ 累積的紀律教訓。
通用任務開單器 SKILL — 統一建立或回寫 Markdown task card、docs/tasks/tasks-*.json 分片、UI quality shard，並強制遵守 docs/agent-briefs/Readme.md (doc_ai_0023) 與 docs/遊戲規格文件/系統規格書/名詞定義文件.md (doc_spec_0008) 的硬規則。USE FOR: 開任務卡、開單、task card、task shard、tasks-ui.json、tasks-prog.json、tasks-dc.json、tasks-data.json、agent-briefs/tasks、docs/tasks/*_task.md、UI pipeline 開卡。DO NOT USE FOR: 純 runtime 除錯、單純修改既有功能碼但不需要新卡、只做極小 typo 修補。
Plan ATM framework refactors by preserving atom/map semantics before splitting large governance modules.
Route natural-language cleanup, refactor, migration, and candidate ranking goals through ATM before local analysis.
Recommend the next official ATM guidance action from current state.
Resolve the current user prompt into an atm.taskIntent.v1 proposal before next-action routing.
| name | atm-lock |
| description | Check, acquire, or release a governed scope lock. |
| argument-hint | <ATM context> |
| charter-invariants-injected | true |
First command:
node atm.mjs next --prompt "$ARGUMENTS" --json
Use this ATM command only after the first command confirms it is the current governed route:
node atm.mjs lock check --json
Mutation safety checks should use ATM guard commands:
node atm.mjs guard mutation --task <task-id> --actor "$ATM_ACTOR_ID" --files <csv> --json
node atm.mjs guard git --task <task-id> --actor "$ATM_ACTOR_ID" --json
node atm.mjs handoff summarize --task "$ARGUMENTS" --json
INV-ATM-001 — No second registry (enforcement: gate, breaking change: yes)
Rule: A host project must not create a second AtomicRegistry implementation outside of packages/core or introduce a parallel ID allocation, version tracking, or registry promotion path.INV-ATM-002 — Lock before edit (enforcement: doctor, breaking change: no)
Rule: No governed file mutation may occur without a valid ScopeLock recorded in .atm/locks/ for the current WorkItem. Agents must call atm lock before editing files.INV-ATM-003 — Schema-validated promotion only (enforcement: gate, breaking change: yes)
Rule: An UpgradeProposal must pass all automatedGates (including JSON Schema validation) before promotion. Direct registry mutation that bypasses the UpgradeProposal path is forbidden.INV-ATM-004 — No competing highest authority (enforcement: doctor, breaking change: yes)
Rule: No host project rule, profile, or configuration may declare itself to have authority equal to or higher than the AtomicCharter. Any rule that contradicts an invariant must go through a charter waiver proposal.INV-ATM-005 — Host rule amendments require waiver flow (enforcement: waiver-required, breaking change: no)
Rule: When a host project rule conflicts with a charter invariant, the host must submit a behavior.evolve UpgradeProposal with a charterWaiver field and a linked HumanReviewDecision. Silent override is not permitted.INV-ATM-006 — Framework work tracking stays downstream (enforcement: doctor, breaking change: yes)
Rule: The framework repository must not host coordinating implementation task cards, planning queues, or project-specific work tracking artifacts beyond ATM's own bootstrap/runtime-managed files. Upstream planning cards belong in the coordinating host workspace and may feed evidence back upstream without becoming framework-resident work tracking.INV-ATM-007 — Public framework docs remain English-only (enforcement: doctor, breaking change: yes)
Rule: Public contributor-facing documentation in the framework repository must remain English-only and repository-neutral. Non-English planning notes, local experiments, or downstream operating guidance must live in the coordinating host workspace unless they are translated into neutral English framework documentation.