Where intent
becomes code.
Hanoo is a specification-first workspace where living specs, team conversations, and AI agents converge — so the input to your coding agents is finally as good as the agents themselves.
By invitation · No spam · Unsubscribe anytime
Designed for engineering teams of eight to thirty, already shipping with Claude Code, Cursor, or Devin — and tired of feeding them thin tickets.
2026, the year the input became the bottleneck.
The bottleneck isn't the model. It's the context we feed it.
Coding agents have outgrown the work-management stack built for humans. Tickets are too thin. Docs rot in Confluence. The decisive context — why we're building this, what it must do, how it fits — lives in Slack threads and nobody's memory.
Hanoo treats the specification as the primary artifact. A living document the team writes with an AI co-pilot through conversation, that synthesizes into structured Intent, Requirements, and Design — versioned in Git, ready for agents to execute against.
A workspace shaped like
the work.
Three panels. A tree of specifications, a conversation that writes them, and the artifacts themselves. No tabs to reconcile, no threads to lose.
Requirements: Spec Synthesis
FR-1 The system synthesizes conversation transcripts into structured acceptance criteria with traceable source turns.
FR-2 Human edits to synthesized sections are preserved across re-syntheses — diffs highlight only sections the AI re-authored.
FR-3 Approved specs commit as clean squashed edits to specs/features/<feature>/Requirements.md.
FR-4 A typing caret appears here
From conversation
to pull request, in order.
- 01Intent
Start with why.
Create a node in your spec tree and brainstorm intent with the AI co-pilot. Questions surface the assumptions; the conversation captures the reasoning.
- 02Conversation
Draft in the room.
Two or three teammates talk it through in real time. The co-pilot listens, proposes structure, cites the turns it synthesized from.
- 03Synthesis
Review the diff.
Hanoo synthesizes Requirements, UX, Design. You accept per section. Human edits are preserved. Approved specs squash-commit to Git.
- 04Execution
Hand off to agents.
Tasks reference requirements by ID. Agents get the full spec as context, run in isolation, and return PRs traceable to the section they fulfill.
Built for the new shape of software work.
Intent → Requirements → Design → Tasks, versioned in Git.
No wiki drift. Every spec file is the source of truth the AI reads from and humans edit.
An AI co-pilot that joins the conversation, not another tab.
The co-pilot participates alongside your team — pinning decisions, proposing synthesis, citing its own sources.
The same spec that humans reviewed is what the agent gets.
Tasks carry requirement IDs. Agents run in isolated environments and return PRs traceable to the spec section.
Keep working where you already talk.
Two-way Slack bridge means the co-pilot can participate in threads — conversations become specs without anyone relocating.
A PLAYBOOK.md at every level, inherited down the tree.
Team conventions cascade from root to leaf. Override where you need to. The agent reads them all.
Every PR links to the section of the spec it fulfills.
Review code alongside intent. Argue about requirements instead of guessing at them.
The agents are no longer the constraint. The constraint is how precisely we can describe the thing we want built — and who we can describe it with.
Join the
preview list.
We're inviting in small cohorts of engineering teams already shipping with coding agents. If that's you — and you're as tired of thin tickets as we are — leave your email.
Tell us where to send the invite.
- Early access to the preview cohorts
- Monthly field notes — what we're learning as we build
- No pricing discussion until the product earns it