devbook-collaboration
v1.0.0Review, comment, and hand-off workflows over devbook chapters. Requests a review and hands a chapter to a named reviewer, reviews one against its folder's rules and its evidence, records each finding as a devbook annotation fence beside the passage it is about, runs the approval decision that writes devbook's own approved rung, and sweeps the adopted folders for what is awaiting whom and which approvals have gone stale. An L1 extension: the state it remembers is three ext.devbook-collaboration keys in the chapter's own meta block, so it adds no field to devbook's schema and needs no devbook release of its own. Ships devbook-collaboration:install, which puts its one rule in the repository so both hosts apply it on a matching read.
By Job SchepersLicense: MIT0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 14, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install devbook-collaboration for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install devbook-collaboration@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/JSdotNet/ai-agent-stackClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/devbook-collaboration/.
Plugin files
├── .claude-plugin/plugin.json├── skills/chapter-approve/SKILL.md├── skills/chapter-handoff/SKILL.md├── skills/chapter-review/SKILL.md├── skills/chapter-review-queue/SKILL.md└── skills/install/SKILL.md
Included Skills5
Run the approval decision on a devbook chapter — show the chapter itself with its open annotation fences, flags first and any note raised since approved-at named as such, take approve, revise, or decline from a person, and on approval write devbook's own status: approved rung with approved-by and approved-at while clearing the collaboration state. Use when: approving a chapter, signing off a specification before it becomes work, recording who approved what, weighing objections raised after an approval, or lifting an approval that has gone stale. Triggers on: "approve this chapter", "sign off on this", "record the approval", "is this approved", "the approval is stale", "what was raised since the approval".
Hand a devbook chapter to a named reviewer and produce the brief they start from — what changed, what the reviewer is being asked to judge, and which neighbouring chapters they need. Records the request on the chapter itself so it survives the session. Use when: asking someone to review a chapter, passing devbook work to another person or session, or parking a chapter that needs a decision you cannot make. Triggers on: "hand off this chapter", "ask someone to review", "request review of", "who should review this", "park this for review".
Review one devbook chapter and record the verdict on the chapter itself — check it against its folder's rules, the neighbours it links to, and the evidence it claims, then write each unresolved finding as an annotation fence beside the passage it is about and set the review state. The reviewer's half of a hand-off. Use when: reviewing a devbook chapter, answering a review request, checking whether a chapter is still true, or resolving findings someone left on one. Triggers on: "review this chapter", "review the domain model", "is this chapter still accurate", "answer the review", "resolve the open findings".
Sweep a repository's devbook folders for everything a review pass has left open — chapters awaiting a named reviewer, chapters carrying unresolved notes, chapters cleared and waiting for approval, and approvals that have gone stale because the content changed after they were signed. Reports one queue grouped by who owes the next move. Use when: asking what is waiting on review, what needs approval, whose turn it is, or whether any approval has lapsed. Triggers on: "what is awaiting review", "review queue", "what needs approval", "stale approvals", "whose turn is it", "open findings across the devbook folders".
Install this plugin's chapter-collaboration rule into a repository so both hosts apply it on a matching read, and record it under components.collaboration in .devbook/config.json. Idempotent: run it on first setup, after upgrading the plugin, and to pick up a rule change. Use when: adopting devbook-collaboration, upgrading it, or the review rules are not being applied. Triggers on: "install devbook-collaboration", "set up chapter review", "collaboration install", "collaboration-install".
Plugin manifests1
{
"name": "devbook-collaboration",
"version": "1.0.0",
"description": "Review, comment, and hand-off workflows over devbook chapters. Requests a review and hands a chapter to a named reviewer, reviews one against its folder's rules and its evidence, records each finding as a devbook annotation fence beside the passage it is about, runs the approval decision that writes devbook's own approved rung, and sweeps the adopted folders for what is awaiting whom and which approvals have gone stale. An L1 extension: the state it remembers is three ext.devbook-collaboration keys in the chapter's own meta block, so it adds no field to devbook's schema and needs no devbook release of its own. Ships devbook-collaboration:install, which puts its one rule in the repository so both hosts apply it on a matching read.",
"author": {
"name": "Job Schepers"
},
"license": "MIT",
"keywords": [
"devbook",
"review",
"collaboration",
"hand-off",
"approval",
"governance",
"chapters",
"documentation"
],
"dependencies": [
{
"name": "devbook",
"version": ">=1.0.0 <2.0.0",
"marketplace": "jsdotnet"
}
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[devbook-collaboration on Agent Plugins Marketplace](https://pluginsmp.com/plugins/devbook-collaboration)