Workspace onboarding
BacklogMediumMB
All use cases
use case
Engineering
From backlog to merge, without switching tabs.
Engineering work spreads wider than anyone else's: the decision is in a document, the task on a board, the code on GitHub and the agreement in Slack. muriki pulls all of it around the same issue, so nobody rebuilds the context three times a day.
Get accesscycle · 2 semanasMUR-24
Lançar o early access
14 Ago · 3 subtarefas
AltaEm andamento
Sync offline com Yjs
06 Ago · em revisão
UrgenteEm andamento
Sync offline com Yjs
fechada pelo PR #412
UrgenteConcluído
Convite de time por link
esperando MUR-25
UrgenteBloqueado
PR #412 mergeado
what changes in your cycle
Stop rebuilding the same context three times a day.
None of this is mandatory: each team takes what makes sense and ignores the rest. The module that delivers each item is marked — today only focus is standing.
work comes in here
01
Before the cycle starts
Prioritised backlog
projectsWhat matters sits at the top. Everything else stops shouting.
Fixed-length cycles
projectsTwo weeks, closed scope. What didn't fit rolls over on its own, no meeting required.
Quarterly roadmap
projectsShow leadership where the team stands without building a deck on Friday night.
Team capacity
projectsKnow whether one more fits before you say yes.
Backlog12
Search by subject
BacklogLowGT
This cycle5
Ship the early access
To doHighGT
Calendar MCP server
To doUrgentAL
In progress2
Offline sync with Yjs
In progressUrgentGT
Team invite by link
BlockedHighMB
Done8
The focus timeline
DoneMediumAL
02
While the code moves
Tasks with subtasks
focusBreak the impossible-looking thing down until it's something you can start today.
Explicit dependencies
focusFind out your work is blocked before standup, not during it.
Blocks with a reason
focusStalled work doesn't vanish: it shows why and how long it's been waiting.
Focus blocks on the calendar
focusReserve the time for real. Your calendar stops lying about your day.
03
After the task closes
Technical decisions in docs
docsThat “why did we build it this way?” still has an answer six months later.
Architecture on canvas
canvasDraw the system and click a node to see the work that built it.
Cycle history
projectsYour retro starts written: what shipped, what stalled, what rolled over.
Decision: CRDT on the client
The document is the local source of truth. The migration is being handled inMUR-25Offline sync with Yjs— when it closes, the paragraph below stops being true.
architecturedecided on Jul 28
and leaves here
What is ready lands where the team already is, with nobody copying links or telling people by hand.
- Slackthe team knows it shipped without anyone announcing
- GitHubthe PR closes the task, the task closes the cycle
- Emailwhoever doesn't live in the tool gets the summary
with the agent
What it does for an engineering team
- An open PR becomes a task with owner and due date, and closes itself when the merge lands.
- “What blocked this week's cycle?” returns the stalled task, for how long, and who is waiting.
- A decision thread in Slack becomes a written document, with the tasks it produced already created.
day to day
How the team uses it
- morning
Open focus and see what's yours today, blockers at the top.
- during
The task follows the PR: it changes state without anyone updating two places.
- end of cycle
What shipped, what stalled and what goes back to the backlog, already sorted.
Is your team in the next wave?
Access opens in waves, as the modules become ready. People on the list go first.