claudecodex

bdd-workflow

BDD-enforced feature lifecycle: problem → Gherkin scenarios → design → plan → close, with mutation testing gate at close; /scaffold-bdd-docs copies the bare templates into a project

0 on GitHubby Brent Hooverv1.4.0MITupdated todayworkflow
/

Plugin bdd-workflow from marketplace caderon-pack in brent-hoover/caderon-pack. Commands read from the repo's manifest — today.

What it installs

Skills (4)

  • close-bdd-feature

    Closes out a feature started with start-bdd-feature. Use when implementation is done and you're ready to wrap up. Revisits deferred.md (do now / keep deferred / permanently drop), writes completed.md summarizing what shipped, runs a reviewer over it, and archives the feature docs. Trigger phrases: "

  • godog

    Guide for implementing BDD scenarios in Go using godog (Cucumber for Go). Use when the project is Go and needs step definitions wired to Gherkin .feature files. Covers project layout, step registration patterns, TestMain wiring, table-driven scenarios, and running scenarios.

  • pytest-bdd

    Guide for implementing BDD scenarios in Python using pytest-bdd. Use when the project is Python and needs step definitions wired to Gherkin .feature files. Covers project layout, step definition patterns, fixture injection, scenario parametrization, and running scenarios.

  • start-bdd-feature

    Guides through the full problem → BDD scenarios → design → plan documentation workflow for a new feature. Use when starting any new feature, initiative, or significant piece of work. Not for small, well-understood infrastructure changes with no open design question — use devops:start-devops-task for

Slash commands (3)

  • /bdd-workflow:close-bdd-feature

    Wrap up a feature — revisit deferred work, write the completion record, and archive the docs

  • /bdd-workflow:scaffold-bdd-docs

    Copy the start-bdd-feature doc templates into feature-work/_templates and the flow README into feature-work/

  • /bdd-workflow:start-bdd-feature

    Guided problem → BDD scenarios → design → plan documentation workflow for a new feature

Subagents (4)

  • completion-reviewer

    Reviews a completed.md (and the deferred.md resolution) at the end of the close-bdd-feature workflow, before archiving. Verifies the completion record matches what actually shipped (git diff) and that no Critical deferred item was silently dropped. Read-only — reports findings, does not edit.

  • design-reviewer

    Reviews a design.md and its BDD scenarios produced by the start-bdd-feature workflow. Use immediately after the design doc and feature files are written, before showing them to the user. Checks that the design solves the stated problem, scenarios are complete and well-formed Gherkin, and interfaces/

  • plan-reviewer

    Reviews a plan.md produced by the start-bdd-feature workflow. Use immediately after an implementation plan is written, before showing it to the user. Checks that steps are atomic and verifiable, correctly ordered, traceable to the design, and that every BDD scenario is covered by at least one step.

  • problem-reviewer

    Reviews a problem.md statement produced by the start-bdd-feature workflow. Use immediately after a problem doc is written, before showing it to the user. Checks that the problem is stated concretely without leaking solutions, complexity drivers are stated as facts (not solutions), and success criter

View source on GitHub

More from brent-hoover/caderon-pack

All 13 plugins →

core

claudecodex

Always-on skills: code explanation, conventional commits, codebase visualization, code quality, git, and Vue/TypeScript frontend work

14 skills · 3 commands

0

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

14 skills · hooks

0

obsidian

claudecodex

Read and write your Obsidian vault from Claude Code — daily notes, quick capture, and vault browsing via MCP

1 skill · 8 commands · 1 MCP server

0

Guides Claude through problem → design → plan documentation workflow for new features; /scaffold-docs copies the bare templates into a project

2 skills · 3 commands · 4 agents

0

start-project

claudecodex

Seven-phase greenfield project planning: vision → stack → architecture → data models → stories → plan → scaffold, ending in a repo with green architecture tests and red BDD specs (Python/Go)

1 skill · 1 command · 7 agents

0

devops

claudecodex

Kubernetes and Helm skills: manifest generation, security policies, Helm debugging, values management

6 skills · 1 command · 1 agent

0

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain bdd-workflow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins13 plugins