releavo
Sign inStart a project

Idea to release, in one loop

Idea in.Release out.1

Everything in between, requirements, design, code, QA and delivery, runs in one loop your whole team and its AI share. Releavo drafts every doc and story, follows every push and carries each change down the chain. The right person signs it off.

Start a project Sign in

Mai talks the idea through. Releavo turns it into a PRD draft.

  • Approval enforced in the database, not a prompt
  • Pushes only to its own branch
  • Your tool sign-ins never reach the agent
  • Approved versions are never overwritten

1 The product owner approves the brief, PRD and stories. The tech lead approves architecture and the readiness check. QA passes stories. Releavo approves nothing, and the database holds it to that.

§1The handoff is over

What Releavo replaces

  1. 01The status meeting.Everyone opens Releavo to a Home that shows what needs them, and nothing else.
  2. 02Copying stories into Jira.Synced both ways, in the background, after Releavo asks what belongs.
  3. 03The PRD nobody updated.Change one doc and every doc built from it is redrafted for its owner.
  4. 04“Is VD-35 done yet?”The merge request moved it, and the diff was checked against its acceptance criteria.
  5. 05The spec that lived in one head.Requirements, designs, decisions and sign-offs in one place the whole team, the client and every agent read.
  6. 06The release date from a spreadsheet.Forecast from the velocity your team actually delivered.

The AI does the legwork. People make the calls.

§2One loop

Idea to release.
One loop, one teammate.

Releavo doesn't sit at one step of your process. It drafts the plan, breaks it into stories, watches the code land, checks it against what was agreed, and forecasts the release. At every step the same rule holds: the AI does the legwork, a named person decides.

  1. 01Plan Drafts the brief, PRD, UX, prototypes and architecturePO and tech lead approve
  2. 02Break down Epics, stories, acceptance criteriaPO approves
  3. 03Build Builds the story, or works with your own AI tools; follows every pushDevelopers review and merge
  4. 04Verify Test cases, readiness, regression scopeQA passes or fails
  5. 05Release Sprints, forecasts, release notesPM ships
  6. 06Learn Carries every change back up the chainOwners approve the ripple
§3One source of truth

Everything your team agreed.
In one place, and true.

Requirements, designs, code activity, tests, decisions and approvals usually live in six tools and three people's heads. Releavo pulls them into one loop and keeps it current, so your team, your client and every AI agent work from the same context. Not a copy of last month's.

Comes in
  • Jira and LinearIssues, sprints, who owns what
  • Confluence and NotionThe pages the team already wrote
  • GitHub, GitLab, Azure DevOpsEvery push and merge request
  • FigmaFrames, components, comments
  • Uploads and voice notesWorkshop notes, spreadsheets, decks, a two-minute ramble
Kept in Releavo
Every version
Brief to stories, each built from the one before. Never overwritten.
Every sign-off
Who approved what, when, and what it was built from.
Every decision
The questions asked, who answered, and where it landed.
Where things stand
Stories, sprints, risks, the release date and why it moved.
Versioned, signed, searchable. The agent reads all of it before it writes a word.
Goes out
  • A Home for each roleWhat needs you, and nothing else
  • Drafts for each ownerA change ripples down, as drafts
  • Your tools, kept in stepApproved here goes out there
  • Your AI apps, connectedClaude Code, Cursor, ChatGPT, any MCP app
  • A client viewApproved versions and progress, read-only

Built for the long runA product lives for years and people move on. The record stays: why tiers cap at 500 units, who agreed, and which merge request built it.

Built for teams that hand overAgencies and outsourced teams keep the client in the loop with a read-only view, and every sign-off on record. When the work changes hands, the context goes with it.

§4The doc chain

Change one thing.
Watch it ripple.

A project runs on a chain of documents, each built from the one before. When CR-14 changes the pricing model, Releavo follows your change-request playbook down the chain, drafts every update, and tells each owner what's waiting for them. Nobody goes hunting for what went stale.

  1. changes/CR-14 Tiered pricing.mdCR-14proposedapproved by Mai
  2. docs/brief.mdBriefv3 · approvedno change
  3. docs/prd.mdPRDv5 · approvedv5v6 draft waiting for Mai
  4. docs/ux.mdUXv4 · approvedv4v5 draft waiting for Ana
  5. docs/architecture.mdArchitecturev2 · approvedv2v3 draft waiting for Huy
  6. docs/readiness.mdReadinessv2 · passedv2v3 re-check waiting for Huy
  7. planning/stories/VD-35-cart-tiers.storyVD-35v2 · in progressv2v3 draft waiting for Mai

Built fromEvery version records what it was made from. PRD v6 says CR-14 + PRD v5, so a reviewer sees why, not just what.

Told, not broadcastOwners hear about it in their own Home and chat: Huy about architecture, Sara about the test cases that moved. Nobody else gets pinged.

§5Drafts, not overwrites

Nothing it writes is final until someone says so.

Each AI edit lands as the next version of the doc, with a diff, a note on why, and the name of the person who approves it. Approved versions are never overwritten. Roll back to v5 any time.

Product owner
Brief, PRD, epics, stories
Tech lead
Architecture, readiness check
QA
Pass or fail, per story
Client
Reads approved versions, comments
Releavo
Nothing. Ever.
docs/prd.mdv5v6 draft

FR-7 · Volume tiers

Wholesale buyers get a flat 10% off orders over 50 units up to three tiers, set per customer group: 5% from 50 units, 8% from 200, 12% from 500.

Tiers apply to the whole order, after any customer-group price. Discounts do not stack with promo codes. A promo code replaces the tier discount if it's larger; they never stack.

FR-8 · Cart display

The cart shows the discount applied, the tier reached, and how many more units unlock the next one.

Only Mai can approve this. Drafted by Releavo for Mai · +14 −3DiscardApprove v6

Enforced in the database, not in a prompt. If your roles can't approve a doc, no button, script or clever request will.

§6Builds and follows the code

Build it either way.
The story already knows.

Connect the AI tools your team already uses (Claude Code, Cursor, VS Code, ChatGPT, anything that speaks MCP) and they work straight from the story: the criteria, the epic, the architecture, moving the story as they go. Or switch coding on and Releavo builds it itself, as a draft pull request under your name. Either way, every push and merge request reaches Releavo, which finds the story, moves it, and checks the code against what was agreed.

claude · acme/web
  1. $ claude mcp add --transport http releavo https://releavo.app/mcp
  2. > /mcp__releavo__implement VD-35
  3. releavoget_story VD-353 criteria · epic VD-5 · architecture v3
  4. releavoupdate_story VD-35→ In progress
  5. ●Edited api/cart/tiers.ts+84 −6
  6. ●Ran the tests22 passed
  7. releavocomment on VD-35!42 · AC 1–3 covered
Your AI tools, connected. Add Releavo to Claude Code, Cursor, VS Code, Claude or ChatGPT, any app that speaks MCP, and sign in. It reads the story, moves it and comments with the pull request, as you, with your roles. How to connect
VD-35 Releavo builds itDraft PR
releavo/VD-35-cart-tiers
  1. Made releavo/VD-35-cart-tiers from main
  2. Read api/cart/total.ts and the tier tests
  3. Asked Huy: does tier 3 cap at 500 units?
  4. Huy answered
  5. Ran the tests · 22 passed
  6. Opened draft pull request !42
Authored by Huy · Co-authored-by: Releavo
Or Releavo builds it. Switch coding on, and a developer presses Releavo builds it. It works in the project's own dev box, asks when the story is unclear, and opens a draft pull request on its own releavo/ branch, under the name of whoever pressed it. It never touches another branch or merges.
ThenEvery push and merge request, whoever wrote it.
acme/webOpen
!42 VD-35 · tier ids in the cart API
feat/VD-35-tier-ids → main
  • api/cart/tiers.ts+84−6
  • api/cart/total.ts+22−5
  • db/migrations/031_tiers.sql+18
  • web/cart/TierHint.tsx+4−3
Huy opened this 1 minute ago
  1. WebhookSigned by GitLab, verified, bots and drafts dropped
  2. Settle3 events in 40s, batched into one job
  3. Diff4 files read from the repo. Following only ever reads
  4. Playbookrepo-events.md, your rules for code
  5. MatchVD-35 is in the branch name
VD-35In progressIn review
Cart shows the tier reached and what unlocks the next
  • AC 1 · Tier applied after group price
  • AC 2 · Cart shows units to next tier
  • AC 3 · Promo code replaces a smaller tier
ReleavoMoved to In review from !42. AC 3 isn't in this diff: total.ts still adds the promo on top of the tier.
Risk New migration 031_tiers.sql isn't in architecture v3. Told Huy.
§7Design, files and voice

Show it, sketch it,
or just say it.

Designs stay in Figma and show up live where they're needed. No designer yet? Releavo sketches a clickable prototype. Drop in the spreadsheet the idea came from, or talk instead of typing. All of it lands in the same loop.

Figma, live in the story. A frame link shows the real design, kept current. Releavo reads it against the acceptance criteria, and with your own Figma paired, edits it with you.
A prototype to click through. Ask for a mockup and Releavo builds one from your PRD, real copy and all. It opens as a live page at phone, tablet and desktop sizes.
Your files, opened in place. Excel with its sheets, Word as pages, slides, PDFs and code, right in the project. Releavo reads them and turns the idea into a brief.
Say it instead of typing it. Hold forth for a minute; Releavo hears names, story keys and your product's words right, in English or Vietnamese, and gets on with it.
§8Works with your tools

Keep your tools.
Releavo keeps them in step.

Connect Jira and Releavo looks around, recommends what to bring in, and asks before moving anything. From then on it syncs in the background: approved here goes out there, changed there comes back. Any MCP server works too.

JiraIssues and sprints, both ways
ConfluenceDocs published and kept current
GitHubPushes and pull requests
GitLabPushes and merge requests
Azure DevOpsAzure Repos, read-only
LinearIssues, projects, cycles
NotionPages and databases
SentryProduction errors for QA
FigmaLive designs, read and edited

Sign-ins stay on Releavo's servers, encrypted. The agent calls your tools through Releavo and never sees a token, and client stakeholders can only read.

§9Delivery

Backlog to release date, without a spreadsheet.

Epics and stories, sprints you plan and close, velocity from what your team actually finished, and a release forecast that moves when scope does. Brought in from Jira or built here.

Velocity
17 pts
Sprint
4 of 6
Release 1.2
14 Nov
Volume Discounts · release 1.2 done scope forecast
04080120startS1S2S3S4S5S61.2 · 14 Nov
Scope grew by 16 points with CR-14. At 17 a sprint, 1.2 still lands in sprint 6.
§10Roles

One agent.
Every hat you wear.

Roles belong to people, per project. Mai is PO and BA on Volume Discounts and a client on Brewline. Releavo works with exactly the roles of whoever's asking, never more. Pick someone:

Product ownerBusiness analyst Releavo, for Mai
It will
  • Draft PRD and story changes
  • Write acceptance criteria
  • Re-prioritise the backlog
  • Ask Huy what a change costs
It hands off
  • Architecture Huy
  • Pass or fail Sara

Split VD-35 into a cart story and a checkout story.

Drafted VD-35 v3 and a new VD-44 for you to approve. Told Huy both need estimating.

Mai approvesBrief, PRD, epics, stories, UXReleavo approves nothing.
§11Playbooks

Your process is a file, not a feature.

There's no change-request button. There's playbooks/change-request.md: plain markdown your team writes and edits. Releavo reads it the way a new hire reads the wiki, then follows it. Change the file and you've changed the process.

  • change-request.mdWrite it up, trace the impact, give the PO options
  • readiness-check.mdIs the architecture ready for stories to start?
  • stories.mdStories, acceptance criteria, traceability to the PRD
  • test-plan.mdTest cases from acceptance criteria, bug reports
  • doc-chain.mdAfter an approval, bring every later doc into step
  • status-update.mdThe weekly note a client can actually read
  • release-notes.mdFrom done stories to release notes
  • uploads.mdRead workshop notes, file them, pull out decisions
§12Under the hood

Works like Claude Code.
In your project, not a repo.

Each job gets its own sandbox with the project's files in it. Releavo reads and edits them, runs Python on a Word doc or a spreadsheet, searches the web, and hands focused work to specialists. Then everything it changed comes back as drafts.

job 7f3afor Mai · PO + BA
  1. readCLAUDE.mdproject index · 31 docs · 9 people
  2. skillchange-requestplaybooks/change-request.md
  3. readchanges/CR-14 Tiered pricing.md
  4. pythonuploads/Pricing workshop.docx3 decisions · 2 open questions
  5. agentarchitectpricing service impact
  6. editdocs/prd.md+14 −3
  7. editplanning/stories/VD-35-cart-tiers.story+6 −2
  8. askHuyCan the cart API take tier ids by 20 Oct?
  9. sync4 drafts0 overwrites
Specialists it hands work to
  1. 01ProductBriefs, PRD sections, scope and what a change costs
  2. 02AnalystStories, acceptance criteria, edge cases, traceability
  3. 03DesignerFlows, every screen state, copy, accessibility
  4. 04ArchitectComponents, data, APIs, technical risk, readiness
  5. 05QATest cases, test plans, regression scope
  6. 06DeliveryWhere the project really is, status for the client
  7. 07LibrarianFinds anything in the project, fast

Word, Excel, PowerPoint and PDF too, and clickable HTML prototypes. It edits a copy of your files, and the copy is a draft.

§13Home

Open it and see what needs you.

Everyone gets a Home built from their roles: what's waiting on their approval, which stories are blocked on them, what they've been asked. Not a feed of everything that happened while they were away.

Mai's Home PO + BA
Waiting for youprd.md v6 · VD-35 v3
Question from HuyShould tier 3 cap at 500 units?
Sprint 311 of 18 points done
Huy's Home Tech lead + Dev
Waiting for youarchitecture.md v3 · readiness re-check
Blocked on youVD-35 needs the tier-id API decision
Your storiesVD-33 in review · VD-35 in progress
Sara's Home QA
Ready to testVD-31 · 4 cases changed by CR-14
Failed last runVD-29 · AC 3, promo stacking
Passed this sprint6 stories

The handoff had a good run.
Start with an idea.
Releavo keeps the loop.

Start a project Sign in Built on Claude