subagent-driven-development
Subagent-Driven Development
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
Project Tool Contract (Warcraft-First)
Use Warcraft workflow tools for task lifecycle operations:
- Check runnable tasks with
warcraft_status - Start each task via
warcraft_worktree_create, then issue the returnedtask()call in the assigned workspace - Preserve completed work with
warcraft_worktree_commit - Finish via
finishing-a-development-branch(which useswarcraft_merge/warcraft_worktree_discard) - Do not replace these lifecycle steps with raw git commands
When to Use
More from minhtri2710/opencode-warcraft
br
>-
1writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
1writing-skills
Use when creating or updating built-in skills so they remain discoverable, testable, and aligned with both upstream superpowers and Warcraft workflows.
1code-reviewer
Use when reviewing implementation changes against an approved plan or task (especially before merging or between Warcraft tasks) to catch missing requirements, YAGNI, dead code, and risky patterns
1executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
1using-git-worktrees
Use when starting implementation work that requires Warcraft-managed task workspaces and reproducible task execution.
1