devbook-procedures

v1.9.0

The five procedures every repository has and no plugin can write: start — how its application comes up; show — how the feature being built is put in front of a reviewer, running and with evidence; capture — how evidence is taken; debug — how a cause is found inside the running application, breakpoints included, without handing the debugger to a person; estimate — how work is sized in story points against the repository's own finished work. Each lands as one editable copy under .agents/skills/ with a managed wrapper per host that carries the fixed goal: the goal is the plugin's and refreshes on upgrade, the procedure is the repository's and is never overwritten once edited. Two skills, init and update, keyed by components.devbook-procedures.adopted in .devbook/config.json. An L1 extension over devbook: it follows devbook's reconcile protocol and stamp, and names no engine.

Claude Code2 Skills

By Job SchepersLicense: MIT0 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes: Claude Code
Parsed components: 2 skill or MCP entries
Source updated: Sep 26, 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-procedures for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install devbook-procedures@agent-plugin-marketplace

Paste 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/devbook

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/devbook-procedures/.

Plugin files

plugins/devbook-procedures/

├── .claude-plugin/plugin.json
├── skills/init/SKILL.md
└── skills/update/SKILL.md

Included Skills2

initskills/init/SKILL.md

Write the repository-owned procedure skills — start, show, capture, debug, estimate — into a repository for the first time, each as one editable copy under .agents/skills/ with a managed wrapper per host carrying the fixed goal, and stamp them under components.devbook-procedures in .devbook/config.json. Refused where that stamp already exists: run devbook-procedures:update. Use when: adopting devbook-procedures. Triggers on: "devbook-procedures init", "install devbook-procedures", "seed the start skill", "seed the show skill", "seed the capture skill", "seed the debug skill", "seed the estimate skill".

updateskills/update/SKILL.md

Move a repository's procedure skills — start, show, capture, debug, estimate — forward after upgrading devbook-procedures or changing which are adopted: refresh every wrapper and every body that still hashes to a shipped seed, seed a newly adopted procedure, orphan a dropped one, and re-stamp components.devbook-procedures. Refused where no stamp exists: run devbook-procedures:init. Use when: upgrading devbook-procedures, a start, show, capture, debug, or estimate skill is missing, or the adopted list changed. Triggers on: "devbook-procedures update", "update devbook-procedures", "upgrade devbook-procedures", "adopt the debug skill", "adopt the estimate skill", "drop the show skill".

Plugin manifests1

plugins/devbook-procedures/.claude-plugin/plugin.json

{
  "name": "devbook-procedures",
  "version": "1.9.0",
  "description": "The five procedures every repository has and no plugin can write: start — how its application comes up; show — how the feature being built is put in front of a reviewer, running and with evidence; capture — how evidence is taken; debug — how a cause is found inside the running application, breakpoints included, without handing the debugger to a person; estimate — how work is sized in story points against the repository's own finished work. Each lands as one editable copy under .agents/skills/ with a managed wrapper per host that carries the fixed goal: the goal is the plugin's and refreshes on upgrade, the procedure is the repository's and is never overwritten once edited. Two skills, init and update, keyed by components.devbook-procedures.adopted in .devbook/config.json. An L1 extension over devbook: it follows devbook's reconcile protocol and stamp, and names no engine.",
  "author": {
    "name": "Job Schepers"
  },
  "license": "MIT",
  "keywords": [
    "devbook",
    "procedures",
    "start",
    "show",
    "capture",
    "debug",
    "estimate",
    "skills",
    "init",
    "update"
  ],
  "dependencies": [
    {
      "name": "devbook",
      "version": ">=1.0.0 <2.0.0",
      "marketplace": "jsdotnet-devbook"
    }
  ]
}

Browse the “devbook” tag →

delivery-schedule

by Job Schepers

The unattended lane, stacked on delivery: the eighteen schedule-* skills that run with nobody watching, plus init and update, plus the catalog of triggers that fires them. Sixteen schedulable entry points that pick their own input and run a flow, a review, a check, a sweep, or a report — devbook validate, devbook verify, devbook update, instruction review, issue sweep, merge review, morning brief, package update, performance review, review, security review, tech update, week starter, weekly cost analysis, weekly update, and what's new — and thirteen trigger definitions naming a target, a cadence, the plugins that target needs, and the prompt for a cloud session that starts with nothing but the repository. delivery-schedule:init creates them through whatever scheduler the live session exposes and stamps the selection under components.schedule, and delivery-schedule:update keeps them level with it; schedule-status reads their runs and logs; schedule-run fires one now. One capability, two host names: Routines in Claude Code, Automations in the GitHub Copilot app. Depends on delivery and names devbook: a trigger whose target is not enabled is reported and skipped, never scheduled.

Claude Code20 Skills

0Updated 1 hour ago

delivery-schedule

by Job Schepers

The unattended lane, stacked on delivery: the eleven schedule-* skills that run with nobody watching, plus install, plus the catalog of triggers that fires them. Nine schedulable entry points that pick their own input and run a flow or a review — bug fix, merge review, package update, performance review, review, security review, week starter, weekly cost analysis, and what's new — and six trigger definitions naming a target, a cadence, the plugins that target needs, and the prompt for a cloud session that starts with nothing but the repository. delivery-schedule:install creates or updates them through whatever scheduler the live session exposes and records the selection under components.schedule; schedule-status reads their runs and logs; schedule-run fires one now. One capability, two host names: Routines in Claude Code, Automations in the GitHub Copilot app. Depends on delivery and names devbook: a trigger whose target is not enabled is reported and skipped, never scheduled.

Claude Code12 Skills

0Updated last week

devbook

by Job Schepers

The devbook convention: arc42/, domain/, tech/, design/, and ai/ folders of addressed Markdown chapters, behaviour captured one rule per chapter into requirements.md and the domain.invariants.md subpages, each chapter carrying a parseable meta block with status ladders, the review triad, and domain/'s two decision rungs — approved, then accepted — with their signatures and content fingerprints, runnable test-case links, a reserved ext namespace, and annotation fences that keep a review note in the chapter beside the passage it is about. Ships the checker — build.mjs, which validates every meta block and reference and writes nothing unless a layered plugin asks it to — the fence writer, the tech/ inventory scripts, three converters between chapters and code (capture-specs, apply-change, verify-change, each over six chapter kinds), validate, annotation-sweep, tech-update, a versioned contract with runnable migrations, and init and update, which put the rules, the tools, and its AGENTS.md section into a repository and keep them current. Ships the shape and the check, never a flow: the delivery engine carries a chapter change, and devbook-derived keeps the committed _meta/ index fresh.

Claude Code8 Skills

0Updated 1 hour ago

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-procedures on Agent Plugins Marketplace](https://pluginsmp.com/plugins/devbook-procedures)

Directory evidence

Install devbook-procedures for Claude Code

Plugin files

Included Skills2

Plugin manifests1

Related plugins

For maintainers

Related plugins