菜单
[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Rendering of the visual progress bar that leader prints after every status.md update. Not triggered by user intent; purely a formatting protocol.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Commit authorship policy: shipper and every other agent must NOT append any Co-authored-by trailer, tooling footer, or bot identity to commit messages. The user is the sole author of every commit produced by the framework.
[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Knowledge-sharing lifecycle: Opt-In → Acquire → Read → Extract → Consent → Upload. Drives when and how the distiller is dispatched, how brain-contributions.md is surfaced to the user, and how approved entries are PR-ed to statsclaw/brain-seedbank.
[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Core orchestration protocol for the StatsClaw 9-agent framework. Defines every gate, state transition, precondition, must-not rule, workflow catalog, and signal-handling policy that the leader enforces.
Enable, disable, or inspect the StatsClaw shared brain — the cross-user knowledge system that lets agents read curated statistical knowledge and optionally contribute back. Use this skill when the user says "turn on brain", "enable brain mode", "turn off brain", "check brain status", "brain on", "brain off", or invokes $brain with on/off/status. Saves the setting to context.md and clones the brain repos if enabling. Full contribution lifecycle lives in skills/brain-sync.
Extract reusable knowledge from the current session, privacy-scrub it, and (with explicit user consent) submit it to the shared StatsClaw brain-seedbank as a pull request. Use this skill when the user says "contribute", "share what I learned", "submit lessons", "add to brain", "contribute knowledge", or invokes $contribute. Bypasses the automatic frequency heuristic but applies the same quality gate and mandatory user-consent step — nothing is uploaded without explicit approval.
[Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] GitHub credential detection and verification. Establishes whether gh CLI, SSH key, $GITHUB_TOKEN, or a credential helper is available before any network-touching work runs.
| name | progress-bar |
| description | [Internal protocol — leader-only. Not a user-invocable skill; do NOT trigger from user input.] Rendering of the visual progress bar that leader prints after every status.md update. Not triggered by user intent; purely a formatting protocol. |
Renders a visual progress bar to the user showing the current workflow state. Leader MUST call this after every status.md update to keep the user informed.
status.mdLeader outputs the progress bar directly as text (markdown) to the user. No tool call needed — just print it.
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress [3/7] │
│ │
│ [✔] Credentials ── [✔] Plan ── [▶] Specs ── [ ] Build/Test │
│ ── [ ] Docs ── [ ] Review ── [ ] Ship │
│ │
│ ▶ Active: planner producing specs... │
│ ⏱ Elapsed: 2m 15s │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress [2/5] │
│ │
│ [✔] Credentials ── [✔] Plan ── [▶] Specs ── [ ] Docs/Implement │
│ ── [ ] Review │
│ │
│ ▶ Active: planner producing specs... │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress (simulation) [4/7] │
│ │
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [▶] Build/Sim/Test │
│ ── [ ] Docs ── [ ] Review ── [ ] Ship │
│ │
│ ▶ Active (parallel): │
│ ├─ builder: implementing estimator in worktree... │
│ ├─ simulator: implementing DGP + harness in worktree... │
│ └─ tester: preparing validation scenarios... │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress (simulation-only) [4/7] │
│ │
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [▶] Sim/Test │
│ ── [ ] Docs ── [ ] Review ── [ ] Ship │
│ │
│ ▶ Active (parallel): │
│ ├─ simulator: implementing DGP + harness in worktree... │
│ └─ tester: preparing validation scenarios... │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress (lightweight) [1/2] │
│ │
│ [▶] Validate ── [ ] Done │
│ │
│ ▶ Active: tester running validation... │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress (simplified) [2/4] │
│ │
│ [✔] Plan ── [▶] Implement ── [ ] Validate ── [ ] Ship │
│ │
│ ▶ Active: builder implementing changes... │
└─────────────────────────────────────────────────────────────────────┘
| State | Step # | Label | Symbol |
|---|---|---|---|
CREDENTIALS_VERIFIED | 1 | Credentials | [✔] when passed |
PLANNED | 2 | Plan | [✔] when impact.md written |
SPEC_READY | 3 | Specs | [✔] when planner completes |
PIPELINES_COMPLETE | 4 | Build/Test | [✔] when builder + tester complete |
DOCUMENTED | 5 | Docs | [✔] when scriber completes |
REVIEW_PASSED | 6 | Review | [✔] when reviewer passes |
DONE | 7 | Ship | [✔] when shipper completes (or skipped) |
| State | Step # | Label |
|---|---|---|
CREDENTIALS_VERIFIED | 1 | Credentials |
PLANNED | 2 | Plan |
SPEC_READY | 3 | Specs |
DOCUMENTED | 4 | Docs/Implement |
REVIEW_PASSED | 5 | Review |
| State | Step # | Label |
|---|---|---|
CREDENTIALS_VERIFIED | 1 | Credentials |
PLANNED | 2 | Plan |
SPEC_READY | 3 | Specs |
PIPELINES_COMPLETE | 4 | Build/Sim/Test |
DOCUMENTED | 5 | Docs |
REVIEW_PASSED | 6 | Review |
DONE | 7 | Ship |
| State | Step # | Label |
|---|---|---|
CREDENTIALS_VERIFIED | 1 | Credentials |
PLANNED | 2 | Plan |
SPEC_READY | 3 | Specs |
PIPELINES_COMPLETE | 4 | Sim/Test |
DOCUMENTED | 5 | Docs |
REVIEW_PASSED | 6 | Review |
DONE | 7 | Ship |
| State | Step # | Label |
|---|---|---|
PLANNED | 1 | Plan |
PIPELINES_COMPLETE | 2 | Implement |
REVIEW_PASSED | 3 | Validate |
DONE | 4 | Ship |
| Symbol | Meaning |
|---|---|
[✔] | Step completed |
[▶] | Step in progress |
[ ] | Step pending |
[✘] | Step failed (BLOCK/STOP) |
[⏸] | Step paused (HOLD — waiting for user) |
When a signal interrupts the workflow, the progress bar shows the interruption:
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress [3/7] │
│ │
│ [✔] Credentials ── [✔] Plan ── [⏸] Specs ── [ ] Build/Test │
│ ── [ ] Docs ── [ ] Review ── [ ] Ship │
│ │
│ ⏸ HOLD: planner needs clarification (see question below) │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress [4/7] │
│ │
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [✘] Build/Test │
│ ── [ ] Docs ── [ ] Review ── [ ] Ship │
│ │
│ ✘ BLOCKED: tester found test failures → respawning builder (1/3) │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress [6/7] │
│ │
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [✔] Build/Test │
│ ── [✔] Docs ── [✘] Review ── [ ] Ship │
│ │
│ ✘ STOPPED: reviewer found isolation breach → respawning builder │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ StatsClaw Progress [7/7] │
│ │
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [✔] Build/Test │
│ ── [✔] Docs ── [✔] Review ── [✔] Ship │
│ │
│ ✔ DONE — All changes shipped successfully │
│ Summary: 3 files changed, PR #42 opened │
└─────────────────────────────────────────────────────────────────────┘
When builder completes and tester runs next, show the active stage:
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [▶] Build/Test │
│ │
│ ▶ Active: builder: implementing changes in worktree... │
└─────────────────────────────────────────────────────────────────────┘
After builder completes:
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [▶] Build/Test │
│ │
│ ▶ Active: tester: running test scenarios... │
└─────────────────────────────────────────────────────────────────────┘
In simulation workflows (11), builder and simulator run in parallel:
│ [✔] Credentials ── [✔] Plan ── [✔] Specs ── [▶] Build/Test │
│ │
│ ▶ Active (parallel): │
│ ├─ builder: implementing changes in worktree... │
│ └─ simulator: implementing DGP in worktree... │
└─────────────────────────────────────────────────────────────────────┘
Leader MUST output the progress bar as markdown text directly after each state transition. This is a text output, not a tool call. Leader constructs the bar from status.md state and the active workflow type.
Minimum frequency: After EVERY status.md write. Optionally also when dispatching a teammate (to show the "Active" line changing).
No separate tool needed — leader simply prints the formatted text block above as part of its response.