Cbrake Claude Plugins
cbrake-claude-plugins is a Claude Code plugin for the Build phase that enforces a documentation-driven workflow using markdown planning before implementing changes.
by cbrake · github.com/cbrake/claude-plugins
Install cbrake’s documentation-driven Claude plugin so planning and implementation stay tied to markdown specs before you change code.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install cbrake-claude-plugins@cbrake/claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:cbrake/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:cbrake/claude-plugins").
What it does
cbrake-claude-plugins is a lean Claude Code plugin collection—one primary bundle—built around documentation-driven development for indie builders. Instead of ad-hoc coding prompts, it steers Claude toward markdown planning artifacts and doc-aligned implementation, which reduces drift when you are the only person defining scope, writing specs, and shipping features. Register it when you are in validate to shape what you will build, then lean on it throughout build docs and lightweight PM rituals as you update specifications alongside code. The public metadata highlights planning, workflow, and implementing changes from documentation rather than niche integrations, so expect process support more than a turnkey SaaS connector. Complexity is beginner to intermediate depending on how strictly you enforce doc gates. Confidence is moderate because detailed SKILL.md triggers were not inlined in the catalog ingest.
Highlights
- Single-plugin Claude Code bundle focused on documentation-driven development and markdown-first planning.
- Workflow-oriented keywords: plan in docs, then implement changes with agent assistance aligned to written specs.
- Suited to solo builders who want Claude to respect doc structure instead of jumping straight to patches.
- Community listing (cbrake/claude-plugins) aimed at general development rather than one vendor API.
- Pairs naturally with validate-time scoping before you enter build implementation.
Why builders use it
Solo builders lose alignment when Claude edits code without an up-to-date markdown plan, causing rework and unclear scope.
After install, Claude follows documentation-driven steps—plan in markdown, then implement—so changes trace back to explicit written intent.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 5 stars, 0 votes.
FAQ
Who is cbrake-claude-plugins for?
It is for Claude Code users who practice documentation-driven development and want one plugin that emphasizes markdown planning before code changes.
When should I use cbrake-claude-plugins?
Use it when scoping a feature in validate and throughout build whenever you update specs and want Claude to implement against those docs.
How do I add cbrake-claude-plugins to my agent?
Add the cbrake/claude-plugins marketplace or plugin path in Claude Code, install the bundled plugin, and follow its README for slash commands or skills that reference your markdown docs.
Comments
Share how you use cbrake-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.