Aiwg issue-driven-al
Orchestrates issue-driven agent loops that post cycle status to issue threads and incorporate human feedback in each cycle.
git clone https://github.com/jmagly/aiwg
T=$(mktemp -d) && git clone --depth=1 https://github.com/jmagly/aiwg "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.agents/skills/issue-driven-al" ~/.claude/skills/jmagly-aiwg-issue-driven-al && rm -rf "$T"
.agents/skills/issue-driven-al/SKILL.mdIssue-Driven Agent Loop Skill
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "work through the bugs" → issue-driven loop shorthand
- "address the backlog" → iterative issue queue processing
- "tackle issue [N]" → single-issue loop
Purpose
Transforms the issue tracker from a passive record into an active 2-way collaboration surface. Each Al cycle posts structured status to the issue thread, scans for human feedback, and responds substantively. The human can monitor and steer agent work asynchronously by commenting on the issue.
Behavior
When triggered, this skill invokes the
/address-issues command with appropriate parameters extracted from the user's natural language request.
Parameter Extraction
| User Says | Extracted Parameters |
|---|---|
| "address issues 17 18 19" | |
| "fix open bugs" | |
| "work on the bug backlog" | |
| "tackle issue 17" | |
| "go through all open issues" | |
| "address the open issues interactively" | |
| "focus on security bugs" | |
| "fix bugs 17-19, they're all auth related" | |
Parameter Support
This skill supports the standard AIWG
--interactive and --guidance parameters:
: When detected in user intent (e.g., "interactively", "walk me through"), adds --interactive
--interactive to invoke discovery questions before starting and pause between issues for human go/no-go.
: When the user provides upfront direction (e.g., "focus on bugs", "skip feature requests", "security first"), extracts the guidance text and passes it via --guidance
--guidance "..." to tailor prioritization and approach without interactive prompts.
Execution Steps
- Parse intent — identify issue numbers, filters, or "all open" from user message
- Invoke
with extracted parameters/address-issues - Monitor execution — the command handles the full cycle protocol
The 3-Step Cycle Protocol
Each cycle of the agent loop follows this protocol:
Step 1: Work — Read issue context, implement fix/feature, run tests
Step 2: Post Status — Post structured comment to the issue thread:
**AL CYCLE #N – [Progress|Blocked|Review Needed]** - Actions taken this cycle - Task checklist (updated) - Blockers (if any) - Next steps
Step 3: Scan & Respond — Read all new thread comments, classify them (feedback/question/approval/correction), and incorporate into the next cycle. Never ignore human input.
Thread Scanning Classification
| Comment Type | Agent Response |
|---|---|
| Feedback | Incorporate into next cycle's work |
| Question | Answer in next status comment |
| Approval | Proceed to next phase or close issue |
| Correction | Adjust approach, acknowledge the change |
| Automated/bot | Ignore |
Completion Criteria (per issue)
An issue is resolved when:
- Implementation is complete
- Tests pass
- Documentation updated (if needed)
- All thread feedback addressed
- No unresolved blocker comments
Multi-Issue Strategy
| Strategy | Trigger |
|---|---|
| Sequential | Default — one issue at a time |
| Batched | When user mentions "related" issues or same module |
| Parallel | When user says "in parallel" (respects context budget) |
Integration
Issue Tracker APIs
Gitea (via MCP tools):
— list issuesmcp__gitea__list_repo_issues
— read issuemcp__gitea__get_issue_by_index
— read threadmcp__gitea__get_issue_comments_by_index
— post statusmcp__gitea__create_issue_comment
— update labels/statusmcp__gitea__edit_issue
GitHub (via
gh CLI):
— list issuesgh issue list
— read issuegh issue view N
— post statusgh issue comment N --body "..."
— close resolvedgh issue close N
Related Commands
| Command | Integration |
|---|---|
| Core loop engine |
| Fetches issues by filter |
| Posts cycle status comments |
| Closes resolved issues |
| Links commits to issues |
Safety
- Never force-push or make destructive git changes
- Always run tests before posting completion status
- Respect
limit (default: 6)--max-cycles - Post status every cycle — transparency is mandatory
- On error, post blocker comment rather than failing silently
- In
mode, pause between issues for human go/no-go--interactive
Configuration
Default settings (overridable via parameters):
- Max cycles per issue: 6
- Strategy: sequential
- Provider: auto-detect from project config
- Branch per issue: false
- Interactive: false
Examples
Fix a specific bug
User: "tackle issue 17" → /address-issues 17
Work through the bug backlog
User: "work on the bug backlog" → /address-issues --filter "status:open label:bug"
Interactive session on multiple issues
User: "address issues 17, 18, 19 interactively" → /address-issues 17 18 19 --interactive
All open issues with higher cycle limit
User: "go through all open issues, give each one up to 8 cycles" → /address-issues --all-open --max-cycles 8
With guidance
User: "fix the open bugs, focus on security issues first" → /address-issues --filter "status:open label:bug" --guidance "Security issues are top priority"
Guidance with batch context
User: "address issues 17, 18, 19 — they're all related to the auth refactor" → /address-issues 17 18 19 --guidance "These are all related to the auth refactor, address them as a batch"
References
- @.aiwg/planning/issue-driven-ralph-loop-design.md - Design document
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/skills/address-issues/SKILL.md - Command definition
- @$AIWG_ROOT/agentic/code/addons/ralph/skills/ralph/SKILL.md - Agent loop command
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/skills/issue-auto-sync/SKILL.md - Issue sync skill
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/context-budget.md - Parallel subagent limits