Founder StoriesShare Your Story
fin𝕏◎
GlobalFounderTimes
Stories of founders. Ideas that inspire.
Where Innovation
Meets Impact.
Submit Your Story
Have a founder story?

Share the problem, the decision and the result.

Submit Your Story
Technology · News analysis · GlobalFounderTimes Editorial

Before the Agent Writes Code, Someone Must Decide What to Build

Published October 25, 2026 · Coverage: August 2026

Event / announcement: August 19, 2026

Jira Planner’s early-access introduction puts the specification, rather than the code editor, at the centre of an AI development workflow.

Mike Cannon-Brookes, Atlassian co-founder. Official press-kit photograph; not a photograph of the event covered.
Mike Cannon-Brookes, Atlassian co-founder. Official press-kit photograph; not a photograph of the event covered. Credit: Atlassian press kit.

Faster execution can make an unclear brief more expensive. If a team has not agreed on the result, an agent can produce the wrong work at remarkable speed. Atlassian’s introduction of Jira Planner in August targeted that gap between an initial idea and instructions detailed enough to execute.

The August 19 announcement described a tool that asks follow-up questions, uses code and organisational context, and turns plans into editable Confluence Live Docs. A completed plan can then become Jira work items with dependencies, milestones and acceptance criteria. The stated aim is to make scope and constraints explicit before agents start building.

At announcement, Jira Planner was in Early Access for Jira Cloud customers with Rovo enabled and Teamwork Graph connected, with Confluence also required. Atlassian said access was rolling out in waves. That is different from unrestricted availability, and the article should be read as coverage of the announced early-access product.

GFT analysis: the management problem here is older than AI. An instruction such as ‘improve onboarding’ hides unresolved decisions about the customer, the point of failure and the definition of improvement. A specification makes those choices visible. An agent does not eliminate the need for that work; it makes the cost of skipping it easier to encounter.

A founder can apply the underlying discipline without adopting a new planning platform. State the problem in one sentence, define what is included, name what is excluded and describe the evidence that would count as success. Then have another person challenge the brief before implementation. If they interpret it differently, the disagreement is useful information rather than an interruption.

The product’s value will depend on whether its questions improve decisions instead of simply generating longer documents. A plan should make execution clearer and review easier. August’s launch is notable because it recognises an overlooked bottleneck in the AI workflow: the system can help organise the brief, but the people commissioning the work still need to decide whether it is the right brief.

Sources and reporting

Independent editorial coverage based on public sources, with GlobalFounderTimes analysis. No interview, sponsorship, partnership or company endorsement is implied. Company claims are attributed to their source.

More from August 2026