Parallel implementation of multiple similar items using shared patterns. Usage: /batch-implement [type] [items]
Implements multiple similar items in parallel using shared patterns and TDD workflow.
/plugin marketplace add ANcpLua/ancplua-claude-plugins/plugin install workflow-tools@ancplua-claude-pluginsParallel implementation of similar items with shared patterns.
Type: $1 (options: diagnostics|tests|endpoints|features|fixes|migrations) Items: $2 (comma-separated list of items to implement)
RUN ALL PHASES WITHOUT STOPPING.
CRITICAL INSTRUCTIONS:
YOUR NEXT MESSAGE: Launch 1 Task tool call for Phase 1 pattern extraction.
subagent_type: feature-dev:code-explorer
description: "Extract implementation pattern"
prompt: |
TYPE: [insert $1 here]
ITEMS: [insert $2 here]
MISSION: Extract implementation pattern.
FIND:
1. Existing implementations of this type
2. Common code structure
3. Required boilerplate
4. Test patterns
5. Registration/wiring needed
CREATE TEMPLATE:
- File structure
- Code skeleton
- Naming conventions
- Integration points
Output: Implementation template with placeholders
-> IMMEDIATELY proceed to Phase 2 after template extraction.
IMPORTANT: Launch ONE agent PER ITEM in a SINGLE message with MULTIPLE Task tool calls.
Parse the items from $2 (comma-separated) and create one agent per item:
subagent_type: feature-dev:code-architect
description: "Implement [ITEM_NAME]"
prompt: |
IMPLEMENT: [ITEM_NAME from $2]
TYPE: [insert $1 here]
USING TEMPLATE from Phase 1:
FOLLOW TDD:
1. Write failing test
2. Implement feature
3. Verify test passes
4. Add integration test if needed
CHECKLIST:
- [ ] Follows template pattern
- [ ] Unit test written
- [ ] Implementation complete
- [ ] Registered/wired correctly
- [ ] No copy-paste errors
Output: Files created with paths
-> Wait for ALL parallel agents to complete, then IMMEDIATELY proceed to Phase 3.
subagent_type: feature-dev:code-reviewer
description: "Review consistency"
prompt: |
REVIEW all new implementations:
CHECK:
1. Consistent naming across all items
2. No conflicts between items
3. All registrations complete
4. Tests follow same pattern
5. No duplicate code that should be shared
Output: Issues found + recommendations
-> Fix any issues found, then IMMEDIATELY proceed to Phase 4.
Run these commands and report results:
# Build all
dotnet build --no-incremental 2>&1 || npm run build 2>&1 || make build 2>&1
# Run tests for new items
dotnet test 2>&1 || npm test 2>&1 || make test 2>&1
# Lint
dotnet format --verify-no-changes 2>&1 || npm run lint 2>&1 || make lint 2>&1
Based on the type ($1), follow these patterns:
For each diagnostic:
Descriptors.csSupportedDiagnosticsFor each test area:
For each endpoint:
For each fix:
For each migration:
After Phase 4, provide this summary table:
| Item | Status | Files | Tests |
|---|---|---|---|
| [item1] | Done/Failed | [paths] | Pass/Fail |
| [item2] | Done/Failed | [paths] | Pass/Fail |
| ... | ... | ... | ... |
Total: X/Y items implemented successfully