pdca-batch

name	pdca-batch
classification	workflow
classification-reason	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
argument-hint	[status|plan|manage]
user-invocable	true
allowed-tools	["Read","Write","Glob","Grep","Bash","Task","TaskCreate","TaskList","AskUserQuestion"]
imports	[]
next-skill	null
pdca-phase	null
task-template	[Batch] {action}

PDCA Batch Skill

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.

1. Read .bkit/state/pdca-status.json
2. Filter to active features (exclude archived/completed unless --all flag)
3. For each feature, display: phase, matchRate, iterationCount, last updated
4. Show summary: total active, total completed, total archived
5. 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.

1. Parse feature names from arguments (space-separated)
2. Validate: max 5 features per batch plan
3. Check current active feature count (max 3 concurrent)
4. For features exceeding the parallel limit, queue them
5. Display batch plan summary and ask for confirmation via AskUserQuestion
6. 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: in feature metadata