docs(#1992): add JIRA-driven workflows tracking issues to roadmap

[ralphbean]

Summary

• Filed seven tracking issues for the JIRA-driven workflows backlog: trigger model (JIRA trigger model — define how JIRA events reach fullsend agents #2263), per-agent JIRA support for triage (Add JIRA support to the triage agent #2264), code (Add JIRA support to the code agent #2265), prioritize (Add JIRA support to the prioritize agent #2266), retro (Add JIRA support to the retro agent #2267), review (Add JIRA support to the review agent (tracking) #2268), and identity/credentials (JIRA identity and credential management #2269)
• Added links to all seven plus existing [feature-squad] /fs-refine slash commands only work for GitHub issues, not Jira #1341 (refine) under the JIRA-driven workflows section in docs/roadmap.md

Closes #1992

[github-actions]

Site preview

Preview: https://bdecf23c-site.fullsend-ai.workers.dev

Commit: caed28d6a1502682e02e6ed4a92cfb54f74036d2

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 8:34 PM UTC · Completed 8:44 PM UTC
Commit: caed28d · View workflow run →

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

Review

Findings

Low

• [Missing or stale documentation] docs/roadmap.md:136 — The diff lists 'refine' alongside five existing default agents (triage, code, prioritize, retro, review) in the 'Per-agent JIRA support' line, but no 'refine' agent currently exists as a harness definition or in docs/agents/README.md. However, 'refine' appears to reference a planned capability — the roadmap's Feature refinement section describes this as a future agent area, and docs/agents/icons/COLORS.md already reserves a color for 'refinement'.
  Remediation: Consider adding a brief annotation (e.g., 'refine (planned)') to distinguish the not-yet-implemented agent from the five that already exist.

Info

• [authorization-chain] docs/roadmap.md:133 — The PR references seven newly filed tracking issues (JIRA trigger model — define how JIRA events reach fullsend agents #2263-JIRA identity and credential management #2269). These issues could not be verified via GitHub API, but the PR body claims they exist and the change structure matches the authorized scope exactly. Human reviewer should spot-check that the linked issues exist and align with the stated areas.

[fullsend-ai-review]

[low] Missing or stale documentation

The diff lists refine alongside five existing default agents (triage, code, prioritize, retro, review) in the Per-agent JIRA support line, but no refine agent currently exists as a harness definition or in docs/agents/README.md. However, refine appears to reference a planned capability and the roadmap Feature refinement section describes this as a future agent area.

Suggested fix: Consider adding a brief annotation (e.g., refine (planned)) to distinguish the not-yet-implemented agent from the five that already exist.

[fullsend-ai-review]

[info] authorization-chain

The PR references seven newly filed tracking issues (#2263-#2269). These issues could not be verified via GitHub API, but the PR body claims they exist and the change structure matches the authorized scope exactly. Human reviewer should spot-check that the linked issues exist.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 11:58 AM UTC · Completed 12:14 PM UTC
Commit: caed28d · View workflow run →

[fullsend-ai-retro]

Retro: PR #2272 — docs(#1992): add JIRA-driven workflows tracking issues to roadmap

Workflow went well. This was a clean, docs-only PR by a human author (ralphbean) that added 6 lines to docs/roadmap.md. Single commit, single review cycle, no rework iterations, merged after ~3 days.

Review quality

The review agent produced two findings:

1. Low — "refine (planned)" annotation: Suggested distinguishing the not-yet-implemented refine agent from existing ones. Reasonable but marginal — the entire roadmap section describes future work, so the context already implies "planned."
2. Info — authorization-chain: Noted that linked issues (JIRA trigger model — define how JIRA events reach fullsend agents #2263–JIRA identity and credential management #2269) "could not be verified via GitHub API." These are same-repo issues that the agent should be able to verify with gh issue view. This is a known gap.

Existing coverage

The improvement opportunities I identified are already covered by open issues:

• Issue verification: Review agent should verify file contents before asserting facts about them #1835 (verify file contents before asserting facts), Review agent: cross-reference external identifiers in docs against codebase #2172 (cross-reference external identifiers in docs), Review agent should fetch issue comments, not just title and body #1700 (fetch issue comments)
• Docs review quality: Review orchestrator: add fast path for trivial docs/prompt-only changes #1900 (fast path for trivial docs changes), Review agent provides shallow feedback on documentation PRs #1480 (shallow feedback on docs PRs)

No new proposals needed — existing issues adequately cover the improvement areas.