From awc
Use when the user explicitly invokes /clear-issues or says "clear the backlog". Orchestrates the full issue lifecycle from investigation through close. Explicitly invoked only — not triggered by general conversation about issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/awc:clear-issuesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Main agent orchestrates the full lifecycle of resolving GitHub issues. Each phase has explicit owners. User can override any decision with explicit instruction at any time.
Main agent orchestrates the full lifecycle of resolving GitHub issues. Each phase has explicit owners. User can override any decision with explicit instruction at any time.
Core principle: Issues are investigated before dispatched, implemented in isolated worktrees, reviewed by a separate agent, and only merged after CI passes. No shortcuts.
Explicitly invoke this skill when the user says:
/clear-issuesDo NOT trigger on casual discussion about issues or questions about issue status.
Owner: Main agent
Before picking issues to grill, classify the open issues:
Parent:, Layer:, and Depends on: metadata in their body. Read these fields.Build a dependency map from the metadata. An issue is eligible when:
Depends on: list are closed (merged to target branch), ANDPick up to 3 eligible issues to grill in parallel. Prefer lower layers first — don't grill Layer 2 while Layer 1 issues in the same epic are still open.
/grill-me on up to 3 eligible issues in parallel.Implementer questions queue: While main agent is mid-grill, implementer questions (from previously dispatched issues) queue up. Answer them after the current grill batch completes — unless a question reveals a dependency that would change which issues to grill. In that case, resolve the dependency signal immediately.
Scope discovery: If implementer discovers issue has multiple concerns → it stops, comments on issue, asks main agent. Do NOT broaden scope unilaterally.
Implementer idle time: Implementers are created in Phase 2, after grill clears for their issue. While waiting for their issue to be grilled, the implementer is not created yet — there is no idle time to waste. Questions from newly dispatched implementers are answered normally during subsequent grill cycles.
Owner: Main agent
superpowers:using-git-worktrees skill. Confirm the base branch with user if not obvious.dispatch-template.md and dispatch implementer using the Implementer Dispatch Template.pending → grilling → dispatched → implement → review → CI → merged → closedOwner: Implementer subagent (runs in worktree)
Follow the Implementer Dispatch Template in dispatch-template.md exactly.
Owner: Reviewer subagent
Follow the Reviewer Dispatch Template in dispatch-template.md exactly.
Owner: Main agent
gh run list or PR status badge). If CI is still running → poll every 30s (up to 10 min) until result. If CI is failed or skipped:
CI waiting mechanism: The main agent polls, not the reviewer. Reviewer signals "CI not green" and returns. Main agent owns the wait and dispatches implementer to fix if CI fails.
Conflict handling: If target branch moves while PR is open → main agent detects conflict, dispatches implementer to rebase. Clean rebase → merge. Conflict-resolved changes → reviewer sanity pass before merge. After any rebase, immediately run git diff against the expected state to verify all intended changes survived.
Owner: Main agent
IDLE ─► TRIAGE (classify epics, build dependency map)
│
├──► EPIC (tracking only — closes when all sub-issues close)
│
└──► GRILLING (up to 3 eligible issues in parallel)
│ │
│ └───(per issue: grill-me ready + checklist passes + no blocker)
│ │
│ ▼
│ DISPATCHED ─► IMPLEMENT ─► REVIEW ─► CI ─► MERGED ─► CLOSED
│ (worktree+implementer) (impl on fix rounds)
| │
| unblocks next layer
│
└──► BLOCKED (dependency still open)
(comment added, re-evaluated after each close)
/grill-me is primary signal; main agent checklist is the gate — grill-me declares first, checklist applied after before dispatching.git rebase --skip is a red-line — never skip commits during rebase without first verifying what the skipped commit contains and getting explicit confirmation that skipping is safe.dispatch-template.md for the full rules governing implementer and reviewer subagents.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub amoschenzixuan/agentic-working-contract --plugin awc