skills/pdca-watch/SKILL.md
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, 실시간 대시보드, ライブダッシュボード, 实时仪表板, panel en vivo, tableau de bord.
npx skillsauth add popup-studio-ai/bkit-claude-code pdca-watchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
v2.1.11 Sprint β FR-β4. Wraps
lib/dashboard/watch.jsover CC's/loop(v2.1.71+). Read-only — only consumes state files; never writes. Falls back to a single render when/loopis 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 |
<feature> is provided, use it verbatim..bkit/state/pdca-status.json → primaryFeature, then
activeFeatures[0] as fallback."No active PDCA feature. Start one with /pdca pm <feature>" and exit./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:
pdca-status.features[<feature>]token-ledger.ndjsonphase === 'completed' or phase === 'archived'/loop Support| 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.
.bkit/state/pdca-status.json and .bkit/runtime/token-ledger.ndjson.MAX_TAIL_LINES = 200 regardless of caller input —
defends against pathological NDJSON growth.| 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
/pdca status — single snapshot (no loop)/control trust — trust score informs auto-escalation/pdca-fast-track — Daniel-mode auto-approve checkpointsARGUMENTS:
testing
Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, 스프린트, 스프린트 시작, 스프린트 상태, スプリント, スプリント開始, スプリント状態, 冲刺, 冲刺开始, 冲刺状态, sprint, iniciar sprint, estado sprint, sprint, demarrer sprint, statut sprint, Sprint, Sprint starten, Sprint Status, sprint, avviare sprint, stato sprint, master plan, multi-sprint plan, sprint master plan, 마스터 플랜, 멀티 스프린트 계획, 스프린트 마스터 플랜, マスタープラン, マルチスプリント計画, スプリントマスタープラン, 主计划, 多冲刺计划, 冲刺主计划, plan maestro, plan multi-sprint, plan maestro sprint, plan maître, plan multi-sprint, plan maître sprint, Masterplan, Multi-Sprint-Plan, Sprint-Masterplan, piano principale, piano multi-sprint, piano principale sprint.
tools
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
testing
Manage PDCA checkpoints and rollback — create, list, restore for safe recovery. Rollback events are recorded via lib/audit/audit-logger ACTION_TYPES.rollback_executed. For sprint-level recovery, individual feature rollbacks may be triggered from within sprint phases (sprint itself is forward-only — terminal state is `archived`, not rolled back; v2.1.13). Triggers: rollback, checkpoint, restore, undo, 롤백, 체크포인트, 복원.
testing
QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId> which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.