skills/pdca-batch/SKILL.md
Manage multiple PDCA features as independent parallel cycles (no shared scope/budget). For multiple features that share scope, budget, or timeline as one cohesive initiative, use /sprint (v2.1.13) — sprint groups features into a single 8-phase container, while pdca-batch keeps them independent. Triggers: pdca-batch, batch, multiple features, 다중 기능, 배치.
npx skillsauth add popup-studio-ai/bkit-claude-code pdca-batchInstall 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.
User-invocable skill for managing multiple PDCA features and batch operations.
| Argument | Description | Example |
|----------|-------------|---------|
| (none) | Show all active features (same as status) | /pdca-batch |
| status | Show all active features and their PDCA status | /pdca-batch status |
| plan <f1> <f2> ... | Plan multiple features in sequence | /pdca-batch plan auth search api |
| manage | Interactive dashboard for parallel features | /pdca-batch manage |
Show all active PDCA features and their current status.
.bkit/state/pdca-status.json--all flag)Output Format:
--- PDCA Feature Dashboard ------------------------
Active Features: 2/3 (max)
# Feature Phase Match% Iter Last Updated
1 user-auth check 85% 2/5 10 min ago
2 search-api design - 0/5 2 hours ago
- (1 slot available)
Completed (recent):
3 payment-flow archived 96% 3/5 2 days ago
---------------------------------------------------
Totals: 2 active | 1 completed | 0 stale
Tip: Use /pdca-batch manage for interactive control
Plan multiple features in a batch sequence.
pdca-status.json (state: idle)
b. Create Plan document using plan template
c. Record batch origin: batchId in feature metadataBatch Plan Output:
--- Batch Plan Results ----------------------------
Batch ID: batch-1710842700000
Features planned: 3
Feature Status Plan Document
auth OK docs/01-plan/features/auth.plan.md
search OK docs/01-plan/features/search.plan.md
api-v2 QUEUED (waiting for slot, 2/3 active)
---------------------------------------------------
Next: Run /pdca design <feature> for each planned feature
Constraints:
phase: queuedInteractive dashboard for managing parallel features.
pdca-status.jsonOutput Format:
--- Feature Management Dashboard ------------------
Active Features: 2/3
[1] user-auth (check, 85%, iter 2/5)
Actions: [a]nalyze [i]terate [r]eport [p]ause
[2] search-api (design, -, iter 0/5)
Actions: [d]esign-review [n]ext [p]ause
[Q] user-input (queued, waiting for slot)
Actions: [c]ancel [p]rioritize
---------------------------------------------------
Global Actions:
[s] Switch active feature
[n] New feature (if slot available)
[r] Refresh dashboard
[x] Exit dashboard
---------------------------------------------------
Select feature number or action:
Management Actions:
| Action | Description | |--------|-------------| | Switch feature | Change which feature is "focused" for subsequent /pdca commands | | Prioritize queued | Move a queued feature to next available slot | | Pause feature | Temporarily halt a feature's PDCA progression | | Cancel queued | Remove a feature from the queue | | New feature | Start a new PDCA cycle if slot available |
Features in pdca-status.json with batch support:
{
"user-auth": {
"phase": "check",
"matchRate": 85,
"iterationCount": 2,
"batchId": "batch-1710842700000",
"queuePosition": null,
"lastUpdated": "2026-03-19T10:30:00.000Z"
},
"search-api": {
"phase": "design",
"matchRate": 0,
"iterationCount": 0,
"batchId": "batch-1710842700000",
"queuePosition": null,
"lastUpdated": "2026-03-19T08:30:00.000Z"
},
"api-v2": {
"phase": "queued",
"batchId": "batch-1710842700000",
"queuePosition": 1,
"lastUpdated": "2026-03-19T10:30:00.000Z"
}
}
| Module | Function | Usage |
|--------|----------|-------|
| lib/pdca/status.js | getPdcaStatus() | Read all feature states |
| lib/pdca/status.js | updatePdcaStatus() | Update feature state |
| lib/pdca/state-machine.js | createContext() | Initialize new feature |
| lib/pdca/lifecycle.js | activateQueuedFeature() | Auto-activate from queue |
| lib/audit/audit-logger.js | writeAuditLog() | Record batch operations |
# View all features
/pdca-batch
# Plan multiple features
/pdca-batch plan user-auth search-api payment-flow
# Interactive management
/pdca-batch manage
The /pdca-batch skill complements the main /pdca skill:
| Scope | Use /pdca | Use /pdca-batch | |-------|-----------|-----------------| | Single feature operations | Yes | No | | Multi-feature overview | No | Yes | | Phase transitions | Yes | No (redirects to /pdca) | | Batch planning | No | Yes | | Feature switching | No | Yes (manage) |
When using /pdca commands, they operate on the currently "focused" feature.
Use /pdca-batch manage to switch the focused feature.
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.