Aglabo Deckrd
aglabo-deckrd is a Claude Code plugin for the Build phase that enforces document-driven, AI-assisted BDD with tasks.md specs and red-green-refactor coding rules.
Install when you want AI-assisted delivery locked to documents, BDD scenarios, and red-green-refactor instead of free-form codegen.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install aglabo-deckrd@aglabo/deckrdBuilt 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:aglabo/deckrd") and the paste-ready config with skillselion.get_install_config("plugin:aglabo/deckrd").
What it does
aglabo-deckrd is a Claude Code plugin bundle that treats written documents as the source of truth for AI-assisted behavior-driven development. Solo builders who lose quality when agents jump straight to code can use Deckrd to define goals, tasks, and scenarios first, then let specialized plugins apply assertion-based rules through a strict red-green-refactor loop. The described BDDCoder path focuses on method-level messages and internally handled implementation steps so the agent follows the spec instead of improvising features. It spans early scoping when you are still shaping acceptance criteria, through Build when features land, and into Ship when tests must match documented scenarios. This is a process and testing discipline plugin, not a generic linter or MCP bridge. Expect to invest in maintaining tasks.md and scenario docs; the payoff is repeatable BDD with an agent that codes to the document.
Highlights
- Document-Driven Development framework for AI-assisted BDD workflows
- Enforces strict rules and phased process rather than ad-hoc agent coding
- BDDCoder skill implements red-green-refactor with method-level assertions
- Extracts tests and implementation from specified documents and tasks.md
- 3-plugin bundle from aglabo/deckrd with decision and assertion-oriented keywords
Why builders use it
Agents that code without anchored documents produce features that drift from acceptance criteria and weak tests.
After install, workflows route through documented goals, strict BDD phases, and assertion-driven implementation so code matches written scenarios.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is aglabo-deckrd for?
It is for Claude Code users who practice BDD and want document-first control over how the agent plans, implements, and tests features.
When should I use aglabo-deckrd?
Use it when scoping features into tasks.md, during Build implementation, and when you need Ship-ready tests aligned to written scenarios.
How do I add aglabo-deckrd to my agent?
Add the aglabo/deckrd plugin bundle in Claude Code, enable the Deckrd and BDDCoder-related plugins, and keep goals and scenarios in the documented tasks format the framework expects.
Comments
Share how you use aglabo-deckrd, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.