opsx-apply-subagents
OpenSpec Parallel Agents
Orchestrates concurrent subagents for OpenSpec — one subagent per independent task, serial execution for dependency chains. Supports OPSX, legacy openspec:*, and Codex CLI prompts:* aliases.
See REFERENCE.md for the full command compatibility matrix and round summary template.
Trigger conditions
Enable when any of these are true:
- 2+ changes can run independently
/opsx:apply(or alias) has multiple pending non-conflicting tasks- Batch archiving or
/opsx:bulk-archiveis needed
Concurrency rules
- One subagent per task — never group tasks
- Only dependency-free nodes run in parallel; chains run serially
- No parallel writes to overlapping file regions — downgrade to serial if conflict risk detected
- Wait for all subagents before summarizing
/opsx:apply workflow
- Run
openspec instructions apply --change "<name>" --json→ get tasks + context files - Analyze dependencies — identify independent vs chained tasks
- Spawn one subagent per independent task (strictly parallel)
- Wait for all → mark completed tasks (
- [x]) sequentially to avoid conflicts - Repeat for next unblocked batch
Legacy command mapping
| Legacy | OPSX equivalent |
|---|---|
/openspec:proposal |
/opsx:new + /opsx:ff |
/openspec:apply |
/opsx:apply |
/openspec:archive |
/opsx:archive |
More from costicapuntaru/agentica
write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
9epic-workflow
End-to-end Epic planning — grill requirements, write a PRD, decompose into GitHub issues with dependencies, and create a feature branch for autonomous implementation. Use when starting a new epic, planning a large feature, or when user says "epic workflow", "plan this feature", or "start a new epic".
8github-auto-implement
Autonomous GitHub issue implementation — picks the next ready issue, triages it, implements with TDD, and opens a PR targeting the correct branch (default, epic feature branch, or PR-chained dependency branch). Use when running the autobot daemon, implementing GitHub issues autonomously, or starting the auto-implement loop.
8tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
7grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
7triage-issue
Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.
7