We write about what we're learning as we build Intent — from rethinking software delivery to working with AI every day.
First impressions matter — especially in software delivery tools, where a confusing setup process can quietly cost you a user before they've even seen the product's real value. Too often, onboarding is an afterthought: a static checklist buried in a corner of the screen, easy to …
If you've adopted an OpenSpec-style workflow in your IDE, you already know the appeal: instead of vague tickets, an AI agent writes a proposal, you approve it, the agent implements it, and the change gets archived into a specs folder once it's done. It feels like a huge upgrade o…
Every team has been here: a great idea surfaces in a workshop, gets scribbled into a Jira ticket, and then slowly rots. The description stays frozen at "v1 brainstorm" while the real understanding of the problem lives scattered across comments, Slack threads, and someone's memory…
If you're a product owner, you've probably had this experience: you write a story, hand it to engineering, and get a question back that stops the sprint cold — "wait, we already built something like this," or "this conflicts with a decision we made two months ago." Nobody did any…
If you've ever context-switched between a Jira ticket, a spec doc, and your editor just to answer "wait, what am I actually supposed to build here?" — you know the tax it puts on real work. Today that tax gets a lot smaller: the Intent plugin for Cursor is live, bringing changese…
Documentation has a shelf-life problem. The moment a spec is written as a plan — full of "will be" and "once implemented" — it starts aging. By the time the code ships, the document is already half-wrong. We wanted to fix that, so we redesigned how Intent generates and structures…
Most engineering teams are running two parallel systems that never quite talk to each other: a ticket tracker full of stale requirements, and a documentation tool full of out-of-date wikis. You spend half your planning time bridging the gap between them — and the code itself? It …
Anyone who has shepherded a large feature branch through code review knows the feeling: the diff is enormous, reviewers are overwhelmed, and merging feels like defusing a bomb. The instinct is always to split the work — but keeping those smaller PRs organized and traceable is a p…
Dependency management is one of those invisible tax items on every engineering team. Someone starts a feature, another engineer is quietly touching the same service, and by the time anyone notices the conflict it's review week and the damage is done. The usual fix is process: Sla…