Split monolithic LLM project workflow into task-specific skill workflows #333

Closed
opened 2026-07-07 02:24:31 -05:00 by jcwalker3 · 0 comments
Owner

Problem

The current LLM workflow is becoming too large to paste and too broad to safely apply to every task. PR review/merge, issue creation, and issue implementation have different permissions, gates, reports, and stop conditions. Keeping all rules in one large prompt makes it easier for LLMs to mix modes, over-apply reviewer rules to issue creation, or accidentally perform reviewer mutations during unrelated work.

Required design

Make skills/llm-project-workflow/SKILL.md a small router and move task-specific rules into separate workflow files.

Proposed structure

  • skills/llm-project-workflow/SKILL.md
  • skills/llm-project-workflow/workflows/review-merge-pr.md
  • skills/llm-project-workflow/workflows/create-issue.md
  • skills/llm-project-workflow/workflows/work-issue.md
  • skills/llm-project-workflow/schemas/review-merge-final-report.md
  • skills/llm-project-workflow/schemas/create-issue-final-report.md
  • skills/llm-project-workflow/schemas/work-issue-final-report.md
  • skills/llm-project-workflow/gates/mutation-ledger-rules.md
  • skills/llm-project-workflow/gates/proof-wording-rules.md
  • skills/llm-project-workflow/gates/identity-capability-rules.md

Acceptance criteria

  • SKILL.md is a router, not the full rulebook.
  • SKILL.md requires the agent to identify task mode before mutation.
  • review-merge-pr.md contains PR inventory, queue ordering, validation, review, terminal mutation, merge, cleanup, and final-report rules.
  • create-issue.md contains duplicate search, exact issue capability, issue creation/commenting, and no-PR-mutation rules.
  • work-issue.md contains author workflow rules for implementing an issue, validating, committing, and creating a PR.
  • Mode isolation is explicit: review mode cannot create issues or edit code; issue-creation mode cannot review or merge; work-issue mode cannot approve or merge.
  • Each workflow has a separate final report schema.
  • Existing reviewer prompt hard walls are preserved in review-merge-pr.md.
  • Tests or verifier coverage ensure an agent cannot mutate before loading the required workflow file.
  • Tests or verifier coverage reject reports that use the wrong schema for the selected mode.
## Problem The current LLM workflow is becoming too large to paste and too broad to safely apply to every task. PR review/merge, issue creation, and issue implementation have different permissions, gates, reports, and stop conditions. Keeping all rules in one large prompt makes it easier for LLMs to mix modes, over-apply reviewer rules to issue creation, or accidentally perform reviewer mutations during unrelated work. ## Required design Make `skills/llm-project-workflow/SKILL.md` a small router and move task-specific rules into separate workflow files. ### Proposed structure - `skills/llm-project-workflow/SKILL.md` - `skills/llm-project-workflow/workflows/review-merge-pr.md` - `skills/llm-project-workflow/workflows/create-issue.md` - `skills/llm-project-workflow/workflows/work-issue.md` - `skills/llm-project-workflow/schemas/review-merge-final-report.md` - `skills/llm-project-workflow/schemas/create-issue-final-report.md` - `skills/llm-project-workflow/schemas/work-issue-final-report.md` - `skills/llm-project-workflow/gates/mutation-ledger-rules.md` - `skills/llm-project-workflow/gates/proof-wording-rules.md` - `skills/llm-project-workflow/gates/identity-capability-rules.md` ## Acceptance criteria - [ ] `SKILL.md` is a router, not the full rulebook. - [ ] `SKILL.md` requires the agent to identify task mode before mutation. - [ ] `review-merge-pr.md` contains PR inventory, queue ordering, validation, review, terminal mutation, merge, cleanup, and final-report rules. - [ ] `create-issue.md` contains duplicate search, exact issue capability, issue creation/commenting, and no-PR-mutation rules. - [ ] `work-issue.md` contains author workflow rules for implementing an issue, validating, committing, and creating a PR. - [ ] Mode isolation is explicit: review mode cannot create issues or edit code; issue-creation mode cannot review or merge; work-issue mode cannot approve or merge. - [ ] Each workflow has a separate final report schema. - [ ] Existing reviewer prompt hard walls are preserved in `review-merge-pr.md`. - [ ] Tests or verifier coverage ensure an agent cannot mutate before loading the required workflow file. - [ ] Tests or verifier coverage reject reports that use the wrong schema for the selected mode.
jcwalker3 added the status:in-progress label 2026-07-07 02:31:26 -05:00
sysadmin removed the status:in-progress label 2026-07-07 02:47:05 -05:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#333