agentleFS
Sign inStart free
ww-w-aiww-w-ai/bkit-claude-code/skills/pdca-watch/SKILL.md

pdca-watch

Skill605 starsChanged 3 months agoApache-2.0View on GitHub

Live PDCA dashboard ticking every 30s — reads pdca-status.json + token-ledger.ndjson tail, renders fixed-width panel via CC /loop. Triggers: pdca watch, live dashboard, watch progress

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If <feature> is provided, use it verbatim.

    line 39
  2. Very specific:

    If still no feature → render "No active PDCA feature.

    line 42
  3. Distinctive:

    After max 60 ticks (≈30 min) — caller restarts if more time needed

    line 67
  4. Distinctive:

    No subprocess spawning, no network.

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PDCA Watch — Live Tick Dashboard

v2.1.11 Sprint β FR-β4. Wraps lib/dashboard/watch.js over CC's /loop (v2.1.71+). Read-only — only consumes state files; never writes. Falls back to a single render when /loop is unsupported (E-β4-01).

Arguments

ArgumentDescriptionExample
(none)Auto-resolve active feature from pdca-status.primaryFeature/pdca-watch
<feature>Watch a specific feature by name/pdca-watch bkit-v2111-integrated-enhancement

Behavior

Resolution

  1. If <feature> is provided, use it verbatim.
  2. Else read .bkit/state/pdca-status.json → primaryFeature, then activeFeatures[0] as fallback.
  3. If still no feature → render "No active PDCA feature. Start one with /pdca pm <feature>" and exit.

Tick (every 30s via /loop)

For each tick, lib/dashboard/watch.js#renderTick produces a panel with:

Watch  <feature> — tick N (HH:MM:SS)
─────────────────────────────────────────────────────────────
Phase: <phase>     Match: <%>    Iter: <n / 5>
Tokens: <in> in / <out> out · samples <N>
Est cost: $<USD>
─────────────────────────────────────────────────────────────

Data sources:

  • Phase / matchRate / iterationCount: pdca-status.features[<feature>]
  • Token totals: last 50 lines of token-ledger.ndjson
  • Cost: Sonnet-class flat estimate ($3/Mtok in, $15/Mtok out)

Termination

  • Ctrl-C from user
  • Feature phase === 'completed' or phase === 'archived'
  • After max 60 ticks (≈30 min) — caller restarts if more time needed

CC /loop Support

CC VersionBehavior
≥ 2.1.71Native /loop 30s ticker
< 2.1.71E-β4-01: single render + warning, no loop
UnknownSame as < 2.1.71 (fail-safe)

The check is performed via watch.checkLoopSupport({ ccVersion }) — caller passes the resolved CC version from lib/infra/cc-version-checker.

Security

  • Pure read on .bkit/state/pdca-status.json and .bkit/runtime/token-ledger.ndjson.
  • Tail bounded to MAX_TAIL_LINES = 200 regardless of caller input — defends against pathological NDJSON growth.
  • No subprocess spawning, no network.
  • PII redaction on the ledger is owned by the writer (Token Accountant); watch only reads what's already redacted.

Module Dependencies

ModuleFunctionUsage
lib/dashboard/watch.jsresolveFeature()Auto-detect when no arg
lib/dashboard/watch.jsrenderTick()One frame per tick
lib/dashboard/watch.jstailLedger()NDJSON tail (≤200)
lib/dashboard/watch.jscheckLoopSupport()CC version gate
lib/infra/cc-version-checker.jsgetCurrent()Version source

Examples

# Auto-detect active feature
/pdca-watch

# Watch a specific feature
/pdca-watch bkit-v2111-integrated-enhancement

Related

  • /pdca status — single snapshot (no loop)
  • /control trust — trust score informs auto-escalation
  • /pdca-fast-track — Daniel-mode auto-approve checkpoints

ARGUMENTS:

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free