Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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, 다중 기능, 배치.
.claude/skills/popup-studio-ai-pdca-batch/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | 62% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 53% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 8% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 34% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 68% | 0% |
> 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 controlPlan multiple features in a batch sequence.
a. Initialize feature in pdca-status.json (state: idle) b. Create Plan document using plan template c. Record batch origin: batchId in feature metadata
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 featureConstraints:
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:
json{ "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 |
bash# 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.
Other measured skills in the registry, with their headline benchmark lift.