Menu
Creates phase plan documents from a spec.md Implementation Order. Invoked by spec-writer, not directly.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Orchestrates standalone or caller-batched bug fixes via implementor and reviewer subagents using TDD. Handles bugs and verified review findings sequentially, tracks them in a dated checklist, and commits each fix without disrupting a surrounding PR-resolution batch.
Resolve GitHub PR review comments from humans and Copilot, including reviews already auto-requested or in progress. Use for verified comment resolution, sequential bugfix batching, one-push CI/Copilot cycles, and SHA-aware waits that avoid stale-event loops.
Shared conventions for Go projects. Copyright boilerplate, code quality, GoConvey testing, architecture, and commands. Referenced by go-implementor, go-reviewer, and workflow skills.
Go TDD implementation workflow. References implementation-principles, go-conventions, testing-principles, and agent-conduct.
Review Go implementations against spec acceptance tests. References implementation-principles, go-conventions, testing-principles, and agent-conduct.
Shared cross-language delivery workflow and guidance for implementing the simplest sufficient solution, maximizing reuse of existing code, and avoiding speculative abstractions, dependencies, and refactors. Use when implementing or reviewing code in any language.
Based on SOC occupation classification
| name | phase-creator |
| description | Creates phase plan documents from a spec.md Implementation Order. Invoked by spec-writer, not directly. |
| context | fork |
Read and follow agent-conduct before starting.
You create one phase file per phase from a spec's Implementation Order, formatted for use by the orchestrator skill.
go-implementor/go-reviewer
(determine from project context if not provided).phase<N>.md per phase in the output directory (format below).# Phase <N>: <Phase title from spec>
Ref: [spec.md](spec.md) sections <comma-separated story IDs>
## Instructions
Use the `orchestrator` skill to complete this phase, coordinating
subagents with the `<implementor-skill>` and `<reviewer-skill>`
skills.
## Items
<items - see below>
### Item <N>.<M>: <Story ID> - <Story title>
spec.md section: <Story ID>
<Brief description referencing acceptance test count from spec.>
- [ ] implemented
- [ ] reviewed
### Batch <B> (parallel)
#### Item <N>.<M>: <Story ID> - <Title> [parallel with <others>]
spec.md section: <Story ID>
<Brief description.>
- [ ] implemented
- [ ] reviewed
If a batch depends on a prior batch: ### Batch <B> (parallel, after batch <B-1> is reviewed).
After all parallel items, include:
For parallel batch items, use separate subagents per item.
Launch review subagents using the `<reviewer-skill>` skill
(review all items in the batch together in a single review
pass).
<phase>.<sequence> (e.g. 4.1, 4.2).- [ ] implemented and - [ ] reviewed checkboxes.