A cited map of how your repos fit together. One command from ticket to linked PRs in every repo.
npx skills add oct8-studio/kbeeA ticket, a Figma link or a sentence in. Linked PRs out.
Repos and contracts affected
“Is this what we're building?”Tasks per repo, in order
“Good to build?”Test-first, on branches
Every consumer checked
Linked PRs, merge order
“Open these PRs?”KB stays true
POST /orders/:id/cancel sets the order to cancelled, and returns 409 when the order is already paid.
Consumed by shop-web, which shows “Paid orders can't be cancelled” on a 409.
Click a citation ↓
40export async function cancelOrder(id: string) {41 const order = await db.orders.find(id);42 if (order.status === 'paid') {43 throw new Conflict('paid orders cannot be cancelled');44 }45 order.status = 'cancelled';46 await events.emit('order.cancelled', order);47 return db.orders.save(order);48}
15import { http } from './http';1617export async function cancelOrder(id: string) {18 const res = await http.post(`/orders/${id}/cancel`);19 if (res.status === 409) throw userError("Paid orders can't be cancelled");20 return res.json();21}
No server, no account. Ask it anything with /kbee ask.
shop/ kb/ # lives inside the repo system-map.md # packages, ownership, links repos/<package>/ # overview + conventions contracts/ # producer → consumers decisions/ # architecture decisions features/<slug>/ # spec, plan, status, review gaps.md # open questions manifest.json packages/api/ packages/web/ packages/types/
/kbee init asks, inside is preselected.shop-kb/ # its own git repo system-map.md # repos, ownership, links repos/<repo>/ # overview + conventions contracts/ # producer → consumers decisions/ features/<slug>/ pending.md # waits for PRs to merge gaps.md manifest.json # commit each repo was synced at shop-api/ shop-web/ shop-types/
pending.md./kbee sync after merges./kbee audit adopts docs in any format.
kb/, docs/, ADRs, AGENTS.md, READMEsNever touches your files unless you choose the rewrite.
› /kbee audit found kb/ hand-written · 41 pages · no manifest also AGENTS.md, docs/adr/ (6) ◆ coverage 7 of 9 packages · 23 of 26 routes missing packages/billing, packages/search ◆ accuracy ✗ 3 claims don't match the code orders.md: 404 on paid orders, code: 409 ◆ sources 58 claims have no file reference ◆ kbee needs manifest.json, contracts/, gaps.md ? Rewrite into kbee's layout, or keep yours and add kbee's structure alongside? keep mine ✓ kb/ adopted · ready for /kbee build
Reads the ticket. Posts PR links back, after a yes.
Builds from the frames. Checks the UI against them.
Opens linked PRs. Reads issues as input.
Not connected? Paste the ticket text instead.
/kbee.It picks the right skill for you.
Needs git and a coding agent. Sized for ~10 repos of ~100k lines.
/kbee build <ticket | link | text>Ticket to linked PRs/kbee initSet up or join a KB/kbee auditAdopt existing docs/kbee ask "…"Cited answers/kbee syncKeep the KB true/kbeeStatuskbeeThe one command; routes to the restkbee-initSet up a KB, or join your team's existing onekbee-auditFind, check and adopt an existing KBkbee-featureRun every stage below, start to finishkbee-specSpec, with the affected repos and contractskbee-planTasks per repo, producers before consumerskbee-implementTest-first on kbee/<slug> brancheskbee-reviewCorrectness and contract checks against consumerskbee-shipPush and open cross-linked PRs, after one yeskbee-syncKeep the KB true, including after mergeskbee-kbAsk, expand, add a repo, or fix the KBInstall, then /kbee build your next ticket.
npx skills add oct8-studio/kbee