The context behind the work, one click from the work itself.
Docs and a shared knowledge base that live inside the workspace and link straight to the cards they describe - so the 'why' is never a separate search away from the 'what'.
Shared docs
Specs, briefs and notes written in a clean editor, versioned and open to the whole team.
Wiki-style knowledge base
Onboarding guides, decisions and process docs organized so answers are found, not asked twice.
Linked to the work
Attach a doc to a task or project and the context travels with the card - no hunting through folders.
Knowledge that stays close to the work it explains
A spec buried in a separate tool goes stale the moment work starts. In KITEBED the doc and the task point at each other, so opening a card gives you the reasoning, and opening the doc shows you what shipped.
- Link any doc to a task, a project or a whole board
- Decisions captured where they'll be found again
- Onboarding a new teammate becomes a reading list, not a scavenger hunt
- Summaries from meetings can land straight into the knowledge base
Everything in one place
When the plan, the discussion, the decisions and the record all sit in the same workspace, nothing important lives in a doc the team forgot existed. The board shows what is happening; the docs explain why - and they never drift apart.
The documents a team keeps reaching for.
Specs & briefs
The plan behind a project, linked to the board it drives.
Onboarding guides
The reading list that turns a first week into a running start.
Decisions
Why a choice was made, captured where it'll be found again.
Process docs
The how-we-do-it that stops the same question being asked twice.
Onboarding without the scavenger hunt
When a new teammate joins, the context they need isn't scattered across chats and someone's memory - it's a linked set of docs sitting right beside the boards they'll work. They read the brief, follow it to the project, and see exactly what shipped and why. What used to take a week of asking takes an afternoon of reading.
Knowledge that stays current because it's used
A wiki dies when it lives apart from the work. Because KITEBED docs link to active tasks and projects, they're opened in the normal course of a day - which is exactly what keeps them accurate. The doc you actually use is the doc that stays true.
- A clean editor for specs, notes and guides
- Versioned and open to everyone with access
- Meeting digests can land straight into the base
- Searchable across projects and cohorts
Keep the why next to the work
Bring your docs into the same workspace as your board and let context travel with every task.