Inspiration

AI coding agents can build a feature in minutes, but they only know what the ticket says. Hand one "Make checkout faster" and it guesses. The real context is scattered: a spec in Confluence, decisions buried in comments, the goal behind the work, the people who know the code. People picking up a ticket hit the same wall. We wanted one place that says "this is ready" or "this is exactly what is missing", and then hands over everything.

What it does

Context Pack answers two questions about any Jira work item.

Is it ready to start? An explainable Definition of Ready with six checks:

  • a clear description
  • acceptance criteria
  • an estimate
  • an assignee
  • no open blockers
  • a linked spec

Every gap comes with a one-line fix. Project admins decide what "ready" means for their space: they switch checks on or off, set the minimum description length, or require every check to pass.

What is the full context? One pack built from Jira and Teamwork Graph, covering the six kinds of context a team runs on:

  • Work: the item, its parent, linked work and open blockers.
  • Knowledge: the linked Confluence spec, with its text, owner and last update.
  • People: who to ask (assignee, reporter, spec owner and contributors).
  • Communication: decisions and out-of-scope notes found in comments.
  • Code: linked pull requests and deployments.
  • Assets: linked designs.
  • Plus the goal the work contributes to: the "why" an agent never sees.

The same rules and the same pack power five surfaces:

  1. Issue panel with Readiness, Context and For AI agents tabs.
  2. Readiness board, a project page that checks the top 25 open work items of a space's backlog and ranks them, most ready first, with each gap tagged.
  3. Definition of Ready settings, a project settings page.
  4. Rovo agent "Context Pack" with four actions and a reusable Rovo skill (ready-for-dev).
  5. MCP server (rovo:mcp) exposing the same four tools to any MCP client, with the user's own permissions.

In the demo, a coding agent is pointed at the vague ticket. It checks readiness, refuses to guess, and lists the gaps. On the ready story, it pulls the pack and implements the feature exactly as the spec and decisions say. It writes a test for each acceptance criterion, all 8 tests pass, and it posts its progress back to Jira. It even caught a mismatch between the spec and the code, because the pack carried the spec's text and not just a link.

How we built it

  • Platform: Forge, Runs on Atlassian. No egress, no external services, no paid AI. Node 24 runtime and UI Kit only.
  • Modules: jira:issuePanel, jira:projectPage, jira:projectSettingsPage, 4 action modules, rovo:agent, rovo:skill, rovo:mcp.
  • Jira REST, always as the current user (asUser()), so nobody sees anything they couldn't open in Jira. Settings saves additionally check the user's "Administer projects" permission.
  • Teamwork Graph:
    • Curated queries: jiraWorkItemGoals, jiraWorkItemLinkedExternalPullRequests, jiraWorkItemLinkedExternalDeployments, jiraWorkItemLinkedExternalDesigns, confluencePageOwners and confluencePageContributors.
    • A persisted Cypher query, MATCH (page:ConfluencePage {ari: $pageId}) RETURN page. It brings the spec's text into the pack from a Jira-only install.
    • Every graph call is fail-soft: if the graph is unavailable, the pack is still built from Jira data and says what is missing.
  • Forge Key-Value Storage holds each project's Definition of Ready.
  • Tests: the rules (parsing, readiness and the markdown handoff) are pure functions with 16 unit tests run on Node's built-in test runner.
  • Video: built in HyperFrames from real screen recordings of the production install and a replay of a recorded agent run, then rendered on GitHub Actions.

Bonus prizes

Context Pack meets the requirements of all four bonus prizes:

  • Best Agents (Rovo): a rovo:agent ("Context Pack") with four reusable action modules (get-context-pack, check-readiness, list-ready-items, post-progress) and a rovo:skill (ready-for-dev) that other agents can invoke as tools.
  • Best app with Atlassian MCP: a rovo:mcp module exposes the same four tools through the Atlassian MCP server, with OAuth and the user's own permissions. An open-source SKILL.md lets users add them to third-party agents. The demo shows a real coding agent refusing an unready ticket, then implementing a ready one and posting progress back to Jira.
  • Best Teamwork Graph integration: the pack consumes the Teamwork Graph API: curated queries for goals, pull requests, deployments, designs and the spec page's owners and contributors, and a persisted Cypher query that reads the spec page's text.
  • Best Marketplace published app: submitted for listing as "Context Pack for Jira" (Marketplace review ticket ECOHELP-185385).

Challenges we ran into

  • Jira's create-issue-link endpoint takes the two sides in the opposite order to the GET response. Our first demo blockers pointed the wrong way, so unit tests now guard link direction.
  • Teamwork Graph needed a company_operation operation name and a site query context. Persisted queries had to be registered against the app's full ARI.
  • The first readiness board checked work items one at a time, each with the full context builder, and the page took 12 to 15 seconds to load. One search for every field the checks need, plus parallel remote-link reads, brought the server work down to about 3.3 seconds for 25 items.

Accomplishments that we're proud of

  • One source of truth behind every surface: the panel, the board, the Rovo agent and the MCP tools always give the same answer.
  • The spec's text and the goal reach the coding agent. In the demo, that's exactly how it caught a real inconsistency instead of shipping it.

What we learned

Readiness is the missing step before AI-assisted delivery. An agent that refuses to start on an unready ticket saves more time than one that writes code faster.

What's next

  • Write readiness snapshots back into Teamwork Graph through a connector, so other agents can find what's ready.
  • Add an optional automation to flag work items that move to "In progress" while still not ready.

Built With

Share this project:

Updates

Submission history