Extract create-issue workflow from monolithic LLM project skill #337

New Issue

2026-07-07T02:41:21-05:00

jcwalker3 commented

2026-07-07 02:41:21 -05:00

Part of #333.

Problem

Issue-creation rules currently live inside the monolithic skills/llm-project-workflow/SKILL.md (§A) and scattered templates. The combined prompt mixes issue-filing gates with author implementation and reviewer rules, making it easy for LLMs to perform repo mutations, PR actions, or reviewer operations during issue creation.

Operators need a single durable create-issue workflow file loadable before any issue mutation.

Required behavior

Extract issue-creation-only rules into:

skills/llm-project-workflow/workflows/create-issue.md
skills/llm-project-workflow/schemas/create-issue-final-report.md

SKILL.md task-mode router should route create-issue tasks to create-issue.md instead of inlining rules.

`create-issue.md` must include

Identity/profile/runtime/capability gates (prgs-author; exact create_issue, comment_issue capabilities)
Mode isolation (no review, merge, branch, commit, push, PR, repo-file edits)
Main checkout rule (no repo mutations)
No raw MCP repair during issue creation
No local Gitea fallback during normal issue creation
Duplicate search before mutation with pagination proof
Issue creation scope, content quality, title/body rules
Label/assignee/metadata gates
Comment-on-existing-issue and edit gates
Issue creation/commenting/edit pre-mutation gates
Final report precision, mutation ledger categories, proof wording enforcement
Controller handoff schema (§27)
Stop conditions (§28)
Hard walls: no implementation, no reviewer mutations, no PR creation

`create-issue-final-report.md` must include

Create-issue controller handoff schema with precise mutation categories
Required proof fields: duplicate search terms, pagination proof, issues created/commented/skipped
Mode declaration: create-issue
Reject legacy Workspace mutations field

Out of scope

work-issue.md extraction (PR #336 / prior work)
review-merge-pr.md extraction (#334 / PR #335)
gates/*.md shared rule files (#333 sibling)
Runtime MCP code changes unless needed for workflow retrieval tests

Acceptance criteria

workflows/create-issue.md exists and is self-contained for a full issue-creation run (§0–§28).
schemas/create-issue-final-report.md exists and matches create-issue handoff requirements.
SKILL.md routes create-issue tasks to the extracted workflow.
Tests or verifier coverage reject issue-creation reports that did not load create-issue.md.
Tests or verifier coverage reject work-issue/review-merge schema fields in create-issue final reports.
Canonical prompt hard walls preserved verbatim or by reference (no repo file edits, no PR/branch/commit/push during issue creation).

Duplicate search summary

Searched open issues (limit=500, 54 returned < limit → pagination complete):

#333 — parent split; partially covers but not a dedicated implementable extraction unit (mirrors #334 child pattern for review-merge).
#334 — review-merge extraction only; explicitly out of scope for create-issue.
No existing issue titled or scoped to create-issue workflow extraction.

Part of #333. ## Problem Issue-creation rules currently live inside the monolithic `skills/llm-project-workflow/SKILL.md` (§A) and scattered templates. The combined prompt mixes issue-filing gates with author implementation and reviewer rules, making it easy for LLMs to perform repo mutations, PR actions, or reviewer operations during issue creation. Operators need a single durable `create-issue` workflow file loadable before any issue mutation. ## Required behavior Extract issue-creation-only rules into: - `skills/llm-project-workflow/workflows/create-issue.md` - `skills/llm-project-workflow/schemas/create-issue-final-report.md` `SKILL.md` task-mode router should route `create-issue` tasks to `create-issue.md` instead of inlining rules. ### `create-issue.md` must include - Identity/profile/runtime/capability gates (`prgs-author`; exact `create_issue`, `comment_issue` capabilities) - Mode isolation (no review, merge, branch, commit, push, PR, repo-file edits) - Main checkout rule (no repo mutations) - No raw MCP repair during issue creation - No local Gitea fallback during normal issue creation - Duplicate search before mutation with pagination proof - Issue creation scope, content quality, title/body rules - Label/assignee/metadata gates - Comment-on-existing-issue and edit gates - Issue creation/commenting/edit pre-mutation gates - Final report precision, mutation ledger categories, proof wording enforcement - Controller handoff schema (§27) - Stop conditions (§28) - Hard walls: no implementation, no reviewer mutations, no PR creation ### `create-issue-final-report.md` must include - Create-issue controller handoff schema with precise mutation categories - Required proof fields: duplicate search terms, pagination proof, issues created/commented/skipped - Mode declaration: `create-issue` - Reject legacy `Workspace mutations` field ## Out of scope - `work-issue.md` extraction (PR #336 / prior work) - `review-merge-pr.md` extraction (#334 / PR #335) - `gates/*.md` shared rule files (#333 sibling) - Runtime MCP code changes unless needed for workflow retrieval tests ## Acceptance criteria - [ ] `workflows/create-issue.md` exists and is self-contained for a full issue-creation run (§0–§28). - [ ] `schemas/create-issue-final-report.md` exists and matches create-issue handoff requirements. - [ ] `SKILL.md` routes `create-issue` tasks to the extracted workflow. - [ ] Tests or verifier coverage reject issue-creation reports that did not load `create-issue.md`. - [ ] Tests or verifier coverage reject work-issue/review-merge schema fields in create-issue final reports. - [ ] Canonical prompt hard walls preserved verbatim or by reference (no repo file edits, no PR/branch/commit/push during issue creation). ## Duplicate search summary Searched open issues (`limit=500`, 54 returned < limit → pagination complete): - **#333** — parent split; partially covers but not a dedicated implementable extraction unit (mirrors #334 child pattern for review-merge). - **#334** — review-merge extraction only; explicitly out of scope for create-issue. - No existing issue titled or scoped to create-issue workflow extraction. ## Related - #333 — parent split - #334 — review-merge extraction sibling - PR #336 — work-issue extraction - PR #335 — review-merge extraction

jcwalker3 added the status:in-progress label 2026-07-07 03:22:09 -05:00

jcwalker3 referenced this issue from a commit

2026-07-07 03:23:52 -05:00

feat: add create-issue final-report verifier (#337)

jcwalker3 referenced a pull request that will close this issue

2026-07-07 03:24:03 -05:00

feat: add create-issue final-report verifier (Closes #337) #341

jcwalker3 referenced this issue

2026-07-07 03:44:16 -05:00

feat: add create-issue final-report verifier (Closes #337) #341

sysadmin closed this issue

2026-07-07 03:59:01 -05:00