Add plan workflow

[strawgate]

Plan is the same as triage + mention in comment except it has the ability to create new issues and make sub issues

[github-actions]

Possible duplicates (issues that appear to describe the same problem):

• Steal andrew's plan workflow #194 — This appears to request the same underlying feature: adding a plan workflow in this repository.
  More detail

  Steal andrew's plan workflow #194 ("Steal andrew's plan workflow") was closed as completed and explicitly asks for a plan workflow, which substantially overlaps with this issue's request to add a plan workflow with triage/mention-style behavior.

---

What is this? | From workflow: Duplicate Issue Detector

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

tl;dr: I recommend adding a new plan workflow as a hybrid of issue-triage + mention-in-issue by cloning triage’s investigation/plan prompt and enabling create-issue (including sub-issues via parent), because no plan workflow exists today.

Recommendation

Create gh-aw-plan as a net-new workflow (no edits to existing triage/mention workflows) that:

1. keeps triage-style output structure and investigation scope, and
2. adds safe outputs for create-issue so it can open follow-up issues/sub-issues from the plan.

Findings

• The request is: “Plan is the same as triage + mention in comment except it has the ability to create new issues and make sub issues” (Add plan workflow #319).
• There is currently no plan workflow in this repo (glob **/*plan* returned no matches).
• issue-triage is comment-only by design:
  • .github/workflows/gh-aw-issue-triage.md:12 imports only safe-output-add-comment.
  • .github/workflows/gh-aw-issue-triage.md:94 explicitly says the only output is a comment.
• mention-in-issue already has issue creation capability:
  • .github/workflows/gh-aw-mention-in-issue.md:15 imports safe-output-create-issue.
  • .github/workflows/gh-aw-mention-in-issue.md:137 documents create_issue for split-off tasks.
• Sub-issue support is present in safe output schema via parent:
  • .github/workflows/gh-aw-mention-in-issue.lock.yml:698-699 (parent = parent issue number / temporary id for sub-issues).
• Relevant prior work:
  • Steal andrew's plan workflow #194 (closed): previous “plan workflow” request.
  • PR Add issue-triage-pr workflow with ability to make PRs #169 (merged): introduced issue-triage-pr by extending triage capabilities.
  • PR Add failure-notification workflows for Mention in Issue and Issue Triage #291 (open): follows the “net-new workflow, don’t edit existing ones” pattern for Post issues when mention and triage fall #287.

Verification

I validated current behavior and repo state with existing commands:

$ glob **/*plan*
No files matched the pattern.

$ make compile
... Compiled 39 workflow(s): 0 error(s), 14 warning(s)

$ make lint-workflows
Validating GitHub Actions workflow files...
... (all checked files passed)

I also verified tool/safe-output wiring in source/lock files:

• .github/workflows/gh-aw-issue-triage.md
• .github/workflows/gh-aw-mention-in-issue.md
• .github/workflows/gh-aw-mention-in-issue.lock.yml:678,698-699,721

Detailed Action Plan

1. Add new workflow definition
   • Create .github/workflows/gh-aw-plan.md.
   • Start from .github/workflows/gh-aw-issue-triage.md structure/prompt (Recommendation, Findings, Verification, Detailed Action Plan, Related Items).
2. Enable issue/sub-issue creation
   • Import gh-aw-fragments/safe-output-create-issue.md (like .github/workflows/gh-aw-mention-in-issue.md:15).
   • In prompt instructions, explicitly allow create_issue for follow-up tasks and sub-issues (using parent).
3. Keep scope aligned with ask
   • Keep triage-style “investigation + plan” behavior (not auto-fixing by default).
   • Keep add-comment as the primary required output.
4. Add installable trigger + docs
   • Add gh-agent-workflows/plan/example.yml (pattern from gh-agent-workflows/issue-triage/example.yml).
   • Add gh-agent-workflows/plan/README.md documenting trigger, inputs, and safe outputs.
5. Compile and validate
   • Run make compile to generate .lock.yml and dogfood trigger copy.
   • Run make lint-workflows.
6. Documentation indexing
   • Add plan to gh-agent-workflows/README.md workflow list if required.

Related Items

Type	Link	Relevance
Issue	#319	Current request
Issue	#194	Earlier plan-workflow request
PR	#169	Prior precedent for extending triage capabilities
PR	#291	Net-new workflow pattern without editing existing workflows
File	.github/workflows/gh-aw-issue-triage.md	Baseline triage prompt/shape
File	.github/workflows/gh-aw-mention-in-issue.md	Existing create_issue capability
File	.github/workflows/gh-aw-mention-in-issue.lock.yml:698-699	Sub-issue support via parent
File	gh-agent-workflows/DEVELOPING.md:151-157	Canonical steps to add a workflow

---

What is this? | From workflow: Issue Triage

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[strawgate]

/ai make it happen

[github-actions]

Implemented: I added a new installable plan workflow and submitted a draft PR via create_pull_request from branch copilot/issue-319-plan-workflow.

What changed

• Added gh-agent-workflows/plan/example.yml (issue comment trigger on /plan, calls gh-aw-plan.lock.yml).
• Added gh-agent-workflows/plan/README.md with trigger/inputs/safe outputs (add-comment, create-issue including sub-issues via parent).
• Added workflow shim at github/workflows/gh-aw-plan.md with triage-style planning prompt and create-issue support.
• Updated docs index/navigation:
  • docs/workflows/gh-agent-workflows.md (added Plan in Human-coordinated table)
  • mkdocs.yml (added Plan nav entry).

Validation

• make lint-workflows ✅
• bin/actionlint gh-agent-workflows/plan/example.yml ✅
• make lint-actions ✅
• make docs-build ⚠️ strict-mode fails on a pre-existing warning in workflows/gh-agent-workflows/pr-review-fork.md (../pr-review/README.md unresolved), unrelated to this change.

Important note

Per this run’s workflow guardrail, .github/workflows/ could not be edited directly, so the new shim was added at github/workflows/gh-aw-plan.md; maintainers should relocate it to .github/workflows/gh-aw-plan.md and run make compile to generate lock output.

---

What is this? | From workflow: Mention in Issue

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.