Rethinking Jira, Confluence, and Git for Multi-Layer Products Software teams have spent the last decade debating where requirements should live. Jira and Confluence became the default answer for most organizations — until AI-assisted development started exposing real cracks in that model. With coding agents now consuming, generating, and acting on requirements directly, it’s worth revisiting […]

Read More →

Specs and change proposals live in the repo; Jira still owns Epics, Stories, and the board. You can do both without maintaining two truths: tie one OpenSpec change folder to one Story, leave tasks.md out of Sub-tasks, and link every ticket to openspec/changes/…. Most organizations will not retire Jira; this split is how you get SDD anyway without […]

Read More →