Skip to content

feat(triage-flow): add ticket triage workflow and jira-write skill; release 3.1.12 - #332

Closed
sergepr wants to merge 2 commits into
mainfrom
feat/triage-flow-harness-intake
Closed

feat(triage-flow): add ticket triage workflow and jira-write skill; release 3.1.12#332
sergepr wants to merge 2 commits into
mainfrom
feat/triage-flow-harness-intake

Conversation

@sergepr

@sergepr sergepr commented Aug 28, 2026

Copy link
Copy Markdown

What

Adds triage-flow: a caller-invoked workflow that triages one issue-tracker ticket — intake (redacted via data-collection), requirements elicitation through comment round-trips, and a posted assessment comment on completion. It never mutates ticket status or assignee.

Also adds the jira-write skill: the write-capable counterpart to read-only data-collection (post a comment, transition, reassign — after content-level safety checks).

Release 3.1.11 → 3.1.12.

Commits

0b71725 fix(rosettify-plugins): realign two lightweight-profile tests with shipped profile
e22b8d5 feat(triage-flow): add ticket triage workflow and jira-write skill; release 3.1.12

The test fix is first and standalone on purpose — it repairs breakage that predates this branch (see below), so it can be reviewed independently of the feature.

Changes

Golden source (instructions/r3/core)

  • workflows/triage-flow.md + five phases: intake, elicitation, publish-questions, assess, completion-check
  • skills/jira-write/ + vendor-binding reference

Generated output — all fourteen plugin builds (seven full, seven lightweight), version bumped across every manifest and all three marketplaces. Full and light stay in lockstep, as in prior releases.

Deployment wiring for this repo's own use.mcp.json (Atlassian MCP via headersHelper), agents/jira-mcp-auth-header.sh, agents/jira-triage.config.json.

Pre-existing test breakage, fixed here

Two assertions went stale in 2fcdce8 ("Bring back opus/sol to lightweight"), which changed the lightweight sources without updating the tests. They have been failing on main since — unrelated to triage-flow, but ci-rosettify-plugins fires on this PR (it touches src/rosettify-plugins/**), so they are fixed here to keep the gate green.

  • profiles.test.ts expected the descriptor suffix to contain "lightweight profile"; the committed lightweight.json ships " (lightweight: simpler workflows, smaller models)".
  • profile.e2e.test.ts expected core-copilot-light's architect to resolve to GPT-5.6 Sol; 2fcdce8 put claude-opus-5-high at the head of the light architect list, so it resolves to Claude Opus 5.

Tests updated to match the shipped profile — no source or generator change. Suite goes from 2 failed / 759 passed to 761 passed; typecheck clean.

Security

agents/jira-triage.secrets.json is now gitignored. The config file already claimed it was, but .gitignore did not enforce it — so the first person to follow the setup steps would have had a live Jira Bearer token stageable by git add -A. No token is committed.

Scope limits — deliberate, recorded in the flow's out_of_scope

  • Caller-supplied ticket_key only; no scheduler
  • writes_require_human_confirmation: false for this POC
  • Running triage-flow needs repo-side setup (agents/jira-triage.config.json, .mcp.json, a local secrets file). Without the config the flow stops and reports rather than guessing values.

Reviewer notes

  • agents/jira-triage.config.json carries a real service-account ID and the POC write-gate override. Intentional — flagging it since it lands in history.
  • The lightweight profile's description still promises "smaller models" while lightweight.json currently declares no modelOverrides (removed in 2fcdce8). Left alone here; worth a separate cleanup.

🤖 Generated with Claude Code

sergepr and others added 2 commits August 27, 2026 17:29
…ipped profile

Both assertions went stale in 2fcdce8 ("Bring back opus/sol to lightweight"),
which changed the lightweight sources without updating the tests. They have been
failing on main since:

- profiles.test.ts expected the descriptor suffix to contain "lightweight
  profile"; the committed lightweight.json ships
  " (lightweight: simpler workflows, smaller models)".
- profile.e2e.test.ts expected core-copilot-light's architect to resolve to
  "GPT-5.6 Sol"; 2fcdce8 put claude-opus-5-high at the head of the light
  architect list, so it now resolves to "Claude Opus 5".

Tests updated to match the shipped profile; no source or generator change.
Suite goes from 2 failed / 759 passed to 761 passed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…elease 3.1.12

Adds triage-flow: a caller-invoked workflow that triages one issue-tracker
ticket — intake (redacted via data-collection), requirements elicitation through
comment round-trips, and a posted assessment comment on completion. It never
mutates ticket status or assignee.

Golden source in instructions/r3/core:
- workflows/triage-flow.md plus five phases (intake, elicitation,
  publish-questions, assess, completion-check)
- skills/jira-write — write-capable counterpart to read-only data-collection:
  post a comment, transition, or reassign, after content-level safety checks

Generated into all fourteen plugin builds (seven full, seven lightweight) and
version bumped 3.1.11 -> 3.1.12 across every manifest and all three
marketplaces, keeping full and light in lockstep as in prior releases.

Deployment wiring for this repo's own use: .mcp.json (Atlassian MCP via
headersHelper), agents/jira-mcp-auth-header.sh, agents/jira-triage.config.json.
The Bearer token is not committed; agents/jira-triage.secrets.json is now
gitignored, which the config file already claimed but .gitignore did not
enforce.

Scope limits, deliberate and recorded in the flow's out_of_scope section:
caller-supplied ticket_key only, no scheduler, and writes_require_human_confirmation
is false for this POC. Running triage-flow requires repo-side setup
(agents/jira-triage.config.json, .mcp.json, a local secrets file); without the
config the flow stops and reports rather than guessing values.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@sergepr

sergepr commented Aug 28, 2026

Copy link
Copy Markdown
Author

Superseded by #334, which carries only the triage-flow workflow, jira-write skill, and tool-issue-creation source (no plugins/* regeneration or version bumps — those come from CI). Closing this in favor of #334.

@sergepr
sergepr deleted the feat/triage-flow-harness-intake branch August 28, 2026 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant