audit
View audit logs, decision traces, and session history for AI transparency. ACTION_TYPES (19 entries) include PDCA events (phase_transition, gate_passed/failed,…
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
$ npx -y skills add popup-studio-ai/bkit-claude-code --skill pdca-watch --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/pdca-watchContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: pdca-watch
classification: workflow
classification-reason: Live PDCA dashboard tied to bkit's state machine + token ledger
deprecation-risk: none
effort: low
description: |
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
argument-hint: "[feature]"
user-invocable: true
allowed-tools:
- Read
- Glob
imports: []
next-skill: null
pdca-phase: null
task-template: "[Watch] {feature}"> 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).
| Argument | Description | Example | |----------|-------------|---------| | (none) | Auto-resolve active feature from `pdca-status.primaryFeature` | `/pdca-watch` | | `<feature>` | Watch a specific feature by name | `/pdca-watch bkit-v2111-integrated-enhancement` |
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.
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:
| CC Version | Behavior | |------------|----------| | ≥ 2.1.71 | Native `/loop 30s` ticker | | < 2.1.71 | E-β4-01: single render + warning, no loop | | Unknown | Same 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`.
defends against pathological NDJSON growth.
watch only reads what's already redacted.
| Module | Function | Usage | |--------|----------|-------| | `lib/dashboard/watch.js` | `resolveFeature()` | Auto-detect when no arg | | `lib/dashboard/watch.js` | `renderTick()` | One frame per tick | | `lib/dashboard/watch.js` | `tailLedger()` | NDJSON tail (≤200) | | `lib/dashboard/watch.js` | `checkLoopSupport()` | CC version gate | | `lib/infra/cc-version-checker.js` | `getCurrent()` | Version source |
# Auto-detect active feature /pdca-watch # Watch a specific feature /pdca-watch bkit-v2111-integrated-enhancement
ARGUMENTS:
A Claude Code plugin that verifies AI-generated code against its own design specs. Three commands. Anyone — even someone vibe-coding for the first time — can ship robust, production-quality software.
Repo: popup-studio-ai/bkit-claude-code
View audit logs, decision traces, and session history for AI transparency. ACTION_TYPES (19 entries) include PDCA events (phase_transition, gate_passed/failed,…
bkend.ai authentication — email/social login, JWT tokens, RBAC, session management. Triggers: bkend auth, bkend login, bkend signup, bkend JWT, bkend RBAC
bkend.ai project tutorials (todo to SaaS) and common error troubleshooting. Triggers: bkend tutorial, bkend cookbook, bkend troubleshooting
bkend.ai database — CRUD, column types, filtering, sorting, relations, indexing. Triggers: bkend table, bkend CRUD, bkend column, bkend relation, bkend data
bkend.ai onboarding — MCP setup, resource hierarchy, tenant/user model, first project. Triggers: bkend quickstart, bkend onboarding, bkend setup, bkend MCP
bkend.ai file storage — upload (presigned URL), download (CDN), visibility levels, buckets. Triggers: bkend file, bkend upload, bkend download, bkend storage,…