Hanoo Design-partner program · May 2026
For engineering teams shipping with Claude Code, Cursor, or Devin

Your agents are fast.
Your tickets are
slowing them down.

Your team talks. Your agents ship.

Hanoo turns your team's conversations into the specs your coding agents can execute. We're in closed POCs with a handful of teams and are picking the next five. Bring one feature; we'll write the spec with you, on a call.

No demo, no deck. We'll spec one of your real features live on the call.
Step 1 · Intro call
20 minutes. We listen to how your team works today. No slides.
Step 2 · Live spec
You bring one real feature. We write its first spec with you, end-to-end.
Step 3 · 2-week engagement
Your team runs three features through Hanoo. Specs live in your Git from day one.
№ 003 · Product Act II · The Synthesis

Conversations in.
Cited specs out.

The synthesis step is the heart of Hanoo. To the left, the meeting as it actually happens — overlapping, reversing, half-formed. To the right, what the AI co-pilot produces: a traceable specification, each clause citing the turns it came from.

Input · Conversation six turns, in order
MP
t.07Michael · 09:14

If we re-run synthesis and it clobbers manual edits, that's a blocker. People will stop editing.

SK
t.08Sora · 09:14

we could diff the whole thing — actually just the sections the AI re-authored. Humans' touch survives.

AI
t.09Co-pilot · 09:15

Want me to capture that as a requirement? I hear two claims: preservation of edits, and a scoped diff.

MP
t.10Michael · 09:15

yes, and add: if someone edits directly in git it should merge cleanly.

SK
t.11Sora · 09:16

ok — scope this to Requirements.md for now. Design can follow.

Output · specs/…/Requirements.md v.14
Spec Synthesis · Requirements

Re-synthesis must not clobber human authorship.

FR-1

Human edits to synthesized sections are preserved across re-syntheses.

cites: t.07 t.10
FR-2

Diffs highlight only sections the AI re-authored; manually-edited sections are displayed as untouched.

cites: t.08 t.09
FR-3
Proposed · synthesis #14

Direct edits to Requirements.md in Git merge cleanly back into the workspace view on next sync.

cites: t.10 t.11
5turns of unstructured conversation — meeting transcript, Slack thread, or in-app chat, all equivalent input.
3requirements emitted — each one traceable to the exact turns that motivated it.
0manual edits lost. Re-run synthesis as often as the conversation changes.
1artifact to review, commit, and hand to the agent — the spec itself.
Hanoo
An open letter · to the first five teams
April 24 · 2026
To the head of engineering,
Product management, without the project management.

We built Hanoo because we kept watching the same thing happen on our own team: the coding agents got brilliantly fast, and then sat there, waiting for a human to tell them what to build.

The bottleneck moved. It's not typing code anymore. It's turning a messy conversation into a spec an agent can execute — and that's where most teams are quietly losing hours every day.

We don't have case studies yet. We have a working product, a handful of design-partner teams already in motion, and five more engagements we're opening for the next four weeks.

If any of this sounds like your Monday mornings, I'd like to hear about it.

Michael & team
Michael Park Founder · Hanoo
Design-partner program · May 2026 · pre-launch

Two weeks with our team. One feature shipped.

We're working with a handful of teams this quarter before pricing opens up: live spec sessions with the founders, every integration wired into your stack, and a direct channel to the people who built the product. No engagement fee while you're a design partner.

Inside the engagement
01
The full Hanoo workspace
Every seat, every integration, every feature we have built. Wired into your stack during onboarding — no feature gates.
Full product
02
A spec co-pilot that listens
Our model turns your Slack threads and meeting notes into a first-draft spec your engineers can polish in minutes.
Core engine
03
Live spec session with a founder
We block an hour and write your first production spec together, on the call. Founder-led, never handed off.
60 min · founder-led
04
Slack + GitHub + Linear bridges
Specs flow to and from where your team already works. Our team wires these into your stack during onboarding.
Wired to your stack
05
A private channel with the founders
Not a support queue — a Slack channel with the people who built the product, for the full engagement.
Direct line
06
Specs committed to your Git
Markdown, in your repo, from day one. The workspace mirrors your Git — the repo is the source of truth.
Portable by design
Our side of the deal

Two weeks. Small cohort by design.

  • ✓A shared Slack channel with the founding team, for the full engagement
  • ✓Specs committed to your Git from day one, markdown and portable
  • ✓Pricing only comes up after you've shipped something through Hanoo
  • ✓A candid debrief at the end, even if the answer is “not yet”
Book the 20-minute intro call
You'll hear back within the day
→
No contract
Two weeks, handshake. Walk away whenever, no off-boarding call.
No lock-in
Specs live in your Git. The workspace is a mirror, not the source of truth.
No testimonial ask
If you haven't shipped something through Hanoo in two weeks, we close out cleanly.
Preview · In early design Forge

When the spec is ready, something has to build it.

FORGE is the runtime we're designing for that part of the loop. Bring your own agent — Claude Code, Codex, Cursor — and run it in an ephemeral sandbox your security team will sign off on.

01 No agent state

Ephemeral by design

Tasks run in disposable sandboxes. No persistent agent memory. The PR is the only durable output.

02 Deny by default

Permission-contracted

Every tool call, file path, and network destination is declared upfront. Deny-by-default. Approval gates for the sensitive ones.

03 SIEM-ready

Audit-first

Every call is logged, hash-chained, and exportable to your SIEM. Reviewable by your security team without re-reading commits.

04 One-click dispatch

Wired into Hanoo

One click from a Hanoo spec dispatches a FORGE task. Every run traces back to the thread it came from — one view from conversation to PR, usable as your project-management surface.

Works with the agent you already use

No lock-in on models, no proprietary SDK to adopt. FORGE is the runtime layer — your agent does the work, FORGE is where the work safely happens.