pdca-batch
Skill605 starsChanged 3 months agoApache-2.0View on GitHub
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
1 other project uses a version of this.
Adopted by
Most recently taken up by
- popup-studio-ai/bkit-claude-codeword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- popup-studio-ai/bkit-claude-code★ 605100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- auditSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-quickstartSkill
- bkend-storageSkill
- bkit-evalsSkill
- bkit-exploreSkill
- bkit-rulesSkill
- bkitSkill
- bkit-templatesSkill
- btwSkill
- cc-version-analysisSkill
- claude-code-learningSkill
- code-reviewSkill
- controlSkill
- deploySkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- mobile-appSkill
- pdca-fast-trackSkill
- pdcaSkill
- pdca-watchSkill
- phase-1-schemaSkill
- phase-2-conventionSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- skill-createSkill
- skill-statusSkill
- sprintSkill
- starterSkill
- zero-script-qaSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 77
Check current active feature count (max 3 concurrent)
- Very specific: line 111
Read all active features from pdca-status.json
- Very specific: line 223
When using /pdca commands, they operate on the currently "focused" feature.
- Very specific: line 224
Use /pdca-batch manage to switch the focused feature.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
- Read
.bkit/state/pdca-status.json - Filter to active features (exclude archived/completed unless
--allflag) - 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 controlplan <feature1> <feature2> ...
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:batchIdin 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 featureConstraints:
- 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
State File Schema
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 Dependencies
| 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 |
Usage Examples
# View all features
/pdca-batch
# Plan multiple features
/pdca-batch plan user-auth search-api payment-flow
# Interactive management
/pdca-batch manageIntegration 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

