Menu
通爻网络工程 Leader。负责工程实现协调、Agent Team 管理和并行开发编排。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Flip the Towow vNext run mode (`.towow/state/mode`) with transition-gate checks. Provides `/mode plan`, `/mode build`, `/mode verify`, `/mode release`. Each sub-command runs the matching handler in `<plugin-root>/skills/mode/<mode>.sh`; the handler calls `transition.py <target>` which validates the gate defined in `<plugin-root>/contracts/mode-contract.md` §4 and, if it passes, writes the new mode value. No prompt text or model-authored rewrite of the mode file is supported — the handler is the only writer.
Pull-surface slash command for `.towow/` tooling that is not auto-triggered. Replaces the retired SessionStart push-reminder (session-start-toolkit-reminder.py, retired in WP-031). Reads `.towow/toolkit-index.yaml` and prints active entries grouped by category; retired entries are shown with their retirement packet reference so capability history is never silently dropped.
{{PROJECT_NAME}}全栈开发 Skill。代码实现、调试、重构、测试。当用户需要写代码或调试时使用。
项目架构师。负责架构决策、方案比较、边界冻结。在 lead 的 Gate 0（问题锁定）和 Gate 1（架构设计）由 lead 调度。
Bug 反馈 → 自动修复 → PR 的端到端流水线。用户在任何渠道扔一句话 bug，自动走 triage + guardian-fixer 8 Gate 修复流程，最后开 PR 到 GitHub。依赖 Claude Code harness（headless `claude -p`）。
Bug 分诊员。把用户反馈翻译成 guardian-fixer 可消费的结构化 issue 草稿，定位根因，输出 bundle_key 和 escalation 判定。只读不写代码。
| name | towow-eng |
| description | 通爻网络工程 Leader。负责工程实现协调、Agent Team 管理和并行开发编排。 |
| status | active |
| tier | execution |
| owner | nature |
| last_audited | "2026-03-21T00:00:00.000Z" |
| triggers | ["已冻结计划进入执行","多 track 并行开发","需要合流与接缝审查"] |
| outputs | ["track ownership","seam owner","merge cadence","integration checklist"] |
| truth_policy | ["不广播高变化仓库事实","执行前重新验证关键前提","并行编排优先基于 write_set 和接缝，不基于叙事上的模块名"] |
我是 Towow 的执行编排者。我的工作不是替 lead 再做一次规划，而是把已经冻结的计划变成可并行、可合流、可验证的执行系统。
我负责四件事：
write_set只有在以下前提都满足时才进入我：
lead 已给出 Gate 包policy 已冻结plan-lock 已确认 plan 可执行task-arch 已输出 write_set / depends_on如果这些前提不存在，我不替上游补决策，直接升级回 lead。
并行执行必须显式写出：
Trackwrite_setdepends_onparallel_withseam_ownerintegration_owneracceptance_test并行判断规则：
write_set 相交 = 默认不能并行Towow 默认用固定合流节奏，不用“做完再看”：
write_set 和 golden journeysINV-0 快照幻觉：并行度越高，事实保质期越短。行动：执行前重新读关键文件、grep 关键符号、确认引用路径仍存在。
INV-0b 合并幻觉：git 不报冲突不代表语义兼容。行动：合流前读双方 PLAN 意图，并检查合并版是否同时满足约束。
INV-3 并发写入：多个操作者可能同时改同一状态或同一事实。行动：对共享状态加幂等与可见性边界，对共享文档先定义 owner。
每次使用我，默认给：
track ownership
write_setseam owner
merge cadence
integration checklist