What problem does it solve?
Implementing changes tracked in issue-spec requires strict coordination rules: typed ID allocation, worker delegation, review loops, and rationale publication. This Skill enforces that protocol so Coordinators and workers execute implementations without violating ownership, sequencing, or review constraints.
Core Features & Use Cases
- Execution Mode Selection: Choose between direct implementation, delegated workers, or managed PROCESS packages with one non-Coordinator owner per change-bearing package.
- Typed ID Management: Allocate IDs in the
<TYPE>-<issue><three-digit sequence> format (e.g., QUESTION-1001) scoped to the target issue.
- Review and Repair Loop: Dispatch independent read-only reviewers, route P0/P1 findings back to the original writer, and publish P2 findings as non-blocking comments.
- Use Case: When implementing a design tracked in a higress issue, the Coordinator seals an implementation assignment, dispatches a worker with the role packet, integrates the exact result commit, and publishes line-rationale drafts before human handoff.
Quick Start
Ask the agent to apply the issue-spec workflow to implement the design from a specific issue in the higress-group/higress repository.
