Atlassian's DESIGN.md is here: what we learned testing portable design context in practice
Jun 15, 2026Kylor Hall, Andrew Campbell

Summary
This post evaluates the DESIGN.md format as a portable design context for AI agents. It compares its performance against Atlassian's existing MCP server and AI skills, highlighting trade-offs in token usage, response time, and context sophistication. Key limitations identified for DESIGN.md include its all-at-once context delivery, the necessity of shortening the file at the cost of detail, and its tendency to prompt agents to re-implement components rather than use existing libraries. The post suggests that while DESIGN.md is useful for prototyping, Atlassian's integrated systems offer better abstraction and efficiency for production environments.
More from the AI-Native Software Development Capabilities in Jira trail
- A simpler way to run AI agents in Bitbucket Pipelines
- We’re bringing governed agent loops to the AI-Native SDLC
- How we made vulnerability fixes review-ready with Agentic Pipelines
- Agentic automation in practice: putting standard engineering work on autopilot
- Opening the door to agent autonomy: The architecture behind Rovo’s agent harness