Add Sub-Issue Closer workflow from Peli's Agent Factory

[github-actions]

Summary

This PR adds the Sub-Issue Closer workflow to the agentics repository - a simple, high-value workflow from Peli's Agent Factory that automatically closes parent issues when all their sub-issues are completed.

What This Workflow Does

The Sub-Issue Closer is an automated agent that:

• 🔍 Scans for open parent issues that have sub-issues
• ✅ Checks if ALL sub-issues are closed (100% completion)
• 🔒 Automatically closes parent issues that are fully complete
• 🌳 Processes recursively up the issue hierarchy
• 💬 Adds transparent comments explaining each closure

Why This Is Valuable

• Keeps Issue Tracker Clean: Eliminates the manual task of tracking and closing completed parent issues
• Saves Time: Automatically maintains issue status as work completes
• Provides Clarity: Team can see at a glance which initiatives are done
• Zero Configuration: Works out-of-the-box with GitHub's native sub-issue feature
• Language-Agnostic: Works with any repository using GitHub Issues
• Conservative Approach: Only closes when absolutely certain all sub-issues are done

Source & Validation

• Source: gh-aw/sub-issue-closer.md
• Blog Post: [Meet the Issue & PR Management Workflows]((github.github.io/redacted)
• Operational Status: Successfully deployed and running in the gh-aw repository
• Complexity: Simple, focused workflow (147 lines)
• Dependencies: None - uses only standard GitHub Issues API

What Was Generalized

From the original gh-aw workflow, I:

• ✅ Removed gh-aw-specific references and mood imports
• ✅ Made all instructions repository-agnostic
• ✅ Focused on standard GitHub Issues features only
• ✅ Kept the simple, clean structure
• ✅ Preserved the conservative, transparent approach

Files Added

1. workflows/sub-issue-closer.md - Workflow definition
2. docs/sub-issue-closer.md - Documentation page with examples
3. README.md - Updated to include new workflow in "Triage & Issue Management Workflows" section

Example Scenario

Issue #100: "Feature: Add User Profile"
├── #101: "Design profile page" [CLOSED]
├── #102: "Implement backend API" [CLOSED]
├── #103: "Create frontend UI" [CLOSED]
├── #104: "Write tests" [CLOSED]
└── #105: "Update documentation" [CLOSED]

When the last sub-issue closes, Sub-Issue Closer will:

1. Detect 100% completion (5/5 closed)
2. Automatically close issue [agentic-workflows] Failed runs #100
3. Add comment: "🎉 Automatically closed - All sub-issues completed (5/5)"

Why This Workflow vs. Others Considered

During evaluation, I considered several high-value workflows from Peli's Agent Factory:

Workflow	Merge Rate	Why Not Selected
Sub-Issue Closer	✅ Production	SELECTED - Simple, general, zero dependencies
Glossary Maintainer	100% (10/10)	Too specific to gh-aw docs structure, requires Serena
CI Coach	100% (9/9)	Already have CI Doctor workflow
Mergefest	Operational	Too complex, very specific to gh-aw git workflow
Issue Arborist	77 reports	Complex, creates new issues, high cognitive load

Sub-Issue Closer stood out for its simplicity, general applicability, and zero configuration requirements.

Testing

The workflow:

• ✅ Uses standard GitHub Issues API (no custom tools)
• ✅ Has conservative limits (max 20 closures per run)
• ✅ Runs daily on a fuzzy schedule
• ✅ Can be manually triggered via workflow_dispatch
• ✅ Has read-only permissions (can only modify issue status)

Related Workflows

This complements existing workflows in the repo:

• Issue Triage - Labels and organizes new issues
• Daily Plan - Creates planning issues with sub-tasks

---

Daily Repo Goal Achiever Evaluation: Completed 2026-02-13

• Phase 1: ✅ Repository consistency verified
• Phase 2: ✅ Discovered and adapted high-value workflow from Peli's Agent Factory
• Evaluation log saved to cache memory for future runs

AI generated by Daily Repo Goal Achiever