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, 다중 기능, 배치.
Installation
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Batch PDCA management persists regardless of model advancement
deprecation-risk
none
effort
high
description
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, 다중 기능, 배치.
User-invocable skill for managing multiple PDCA features and batch operations.
Arguments
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
Action Details
status (Default)
Show all active PDCA features and their current status.
Read .bkit/state/pdca-status.json
Filter to active features (exclude archived/completed unless --all flag)
For each feature, display: phase, matchRate, iterationCount, last updated
Show summary: total active, total completed, total archived
Warn if approaching max parallel limit (3)
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 ...
Plan multiple features in a batch sequence.
Parse feature names from arguments (space-separated)
Validate: max 5 features per batch plan
Check current active feature count (max 3 concurrent)
For features exceeding the parallel limit, queue them
Display batch plan summary and ask for confirmation via AskUserQuestion
On confirmation, for each feature sequentially:
a. Initialize feature in pdca-status.json (state: idle)
b. Create Plan document using plan template
c. Record batch origin: batchId in feature metadata
Display batch plan results
Batch 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:
Maximum 5 features per batch plan command
Maximum 3 features active simultaneously
Features beyond the limit are queued with phase: queued
Queued features auto-activate when a slot becomes available
manage
Interactive dashboard for managing parallel features.
Read all active features from pdca-status.json
Display interactive-style management panel
Show available actions per feature
Accept user input for next action via AskUserQuestion
Output 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
Parallel Feature Rules
Maximum 3 concurrent features: Prevents context overload and resource contention
Independent state: Each feature has its own phase, matchRate, and iteration count
Shared guardrails: Automation level and trust score are global (not per-feature)
Queue system: Features beyond limit are queued and auto-activated on slot availability
Isolation: Features do NOT share checkpoints or audit entries
# View all features
/pdca-batch
# Plan multiple features
/pdca-batch plan user-auth search-api payment-flow
# Interactive management
/pdca-batch manage
Integration with /pdca
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.