By gvarela
Workbench for structured software development with TDD, project planning, and beads integration.
Create architectural design decisions based on validated research
Transform design into detailed phased execution plan with embedded tasks
Update status across all project documentation files based on progress
Validate that execution plan was correctly implemented and verify all success criteria
Validate project documentation follows wb workflow correctly
Analyzes codebase implementation details. Finds how specific components work, traces data flow, and documents technical details with precise file:line references.
Finds specific components and files in the codebase. Specializes in locating where features are implemented, which files contain certain functionality, and mapping the codebase structure.
Finds similar patterns and implementations in the codebase. Identifies conventions, recurring patterns, and examples that can guide new implementations.
Analyzes codebase from a product perspective. Explains features as user-visible behaviors, user flows, and product capabilities rather than implementation details. Documents what the software does, not how the code works.
Validates research documents by checking file paths exist, code snippets match actual files, and behavioral claims are accurate against the codebase. Returns structured PASS/FAIL report.
Iterate on UI mockups, capturing keeps/removes/changes with full fidelity. Versions each iteration and maintains decision log.
Enforces project documentation structure in docs/plans/ directories - research.md for facts, design.md for decisions, tasks.md for implementation, thoughts/ for explorations.
Validates research documents against the actual codebase. Checks file paths exist, code snippets match, and behavioral claims are accurate. Use when "validate research", "check research accuracy", "verify research", or "is this research still accurate".
Interactive code review walkthrough using tmux and nvim for pair programming style review. Use when user says "review", "walk through changes", "explain this diff", "prep for PR", or wants to understand what changed.
Monitors beads status and reminds about bd sync at session end or when phases complete.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin for structured software development workflows: project planning, research, design, execution, and validation with TDD enforcement and beads integration.
A personal workbench of tools and workflows for Claude Code. Streamlines software development through structured planning, research, and persistent task tracking with beads.
# Add the marketplace and install the plugin
claude plugin marketplace add gvarela/workbench
claude plugin install wb@gvarela-workbench
For local development:
# Clone and test locally (changes take effect immediately)
git clone [email protected]:gvarela/workbench.git
claude --plugin-dir /path/to/workbench
To release new commands/skills/agents:
Bump version in both .claude-plugin/plugin.json and .claude-plugin/marketplace.json (must match)
Commit and push to GitHub
Users run from their shell (not a slash command):
claude plugin update wb@gvarela-workbench
Restart Claude (or /reload-plugins) to apply
Note: /reload-plugins alone does NOT pull updates — the cache is keyed by version and only claude plugin update invalidates it.
# Initialize -> Research -> Design -> Implement -> Validate
/wb:create_project my-feature docs/plans TICKET-123
/wb:create_research docs/plans/2025-01-15-TICKET-123-my-feature
/wb:create_mockup docs/plans/... "UI component" # Optional for UI
/wb:create_design docs/plans/...
/wb:create_execution docs/plans/...
/wb:implement_tasks docs/plans/...
/wb:validate_execution docs/plans/...
Skills (auto-activated): project-structure, mockup-iteration, tdd-discipline, verification-before-completion, status-sync, review-prep
/wb:*)Slash commands for project documentation and task management:
/wb:create_project - Initialize structured documentation with rich metadata/wb:create_research - Document codebase using parallel research agents/wb:create_mockup - Research UI patterns and create HTML mockups with visual validation/wb:create_design - Create architectural design decisions (WHAT and WHY)/wb:create_execution - Transform design into phased execution plan (HOW)/wb:implement_tasks - Implement with TDD (Red-Green-Refactor)/wb:implement_coordinated - Coordinate implementation with worker agents/wb:validate_execution - Validate implementation matches plan/wb:validate_project - Validate project documentation structure/wb:create_handoff - Create session handoff for work continuity/wb:resume_handoff - Resume from handoff document/wb:update_status - Intelligently sync status across all documentation files/wb:help - Quick reference for all commandsSpecialized agents for codebase analysis:
codebase-locator - Find specific components and filescodebase-analyzer - Analyze implementation details with file:line referencespattern-finder - Find similar patterns and implementationstask-verifier - Verify task completion against requirementsBackground capabilities that Claude automatically invokes:
project-structure - Enforces document separation (research.md, design.md, tasks.md)mockup-iteration - Iterate on UI mockups with KEEP/REMOVE/CHANGE trackingtdd-discipline - Enforces RED-GREEN-REFACTOR cycle before writing production codeverification-before-completion - Requires running verification before claiming work is donestatus-sync - Monitors for status drift and reminds to syncreview-prep - Interactive code review walkthrough using tmux and nvimworkbench/
├── .claude-plugin/ # Plugin manifest + marketplace
│ ├── plugin.json
│ └── marketplace.json
├── commands/ # Slash commands (/wb:*)
├── agents/ # Specialized subagents
├── skills/ # Auto-activated capabilities
├── hooks/ # Event handlers
├── scripts/ # Utility scripts (lint)
├── docs/ # Guides and documentation
└── general/ # General-purpose prompts
Requires beads for persistent task tracking:
bd init --stealth # Stealth: .beads/ not committed (work repos)
bd init # Git: .beads/ in git (personal projects)
Commands create/track beads issues for phases, tasks, and UI questions. SessionStart hook detects mode automatically.
npx claudepluginhub gvarela/workbench --plugin wbA Claude Code plugin for structured, context-efficient software development.
Structured project planning and execution through brainstorm, spec, and build phases across three execution tiers: sequential, delegated sub-agents, and full agent teams
Focused agentic engineering workflow: design-doc, spec, plan, implement, tdd, refactor, review, address-pr-feedback, browser-verify, explain-visually, compress, branch, and commit.
Unified superpowers+beads workflow + proactive template catalog (413+ specialist agents on-demand from claude-code-templates)
Virtual development team: TDD, debugging, code review, backlog management, and proven workflow patterns
AI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI agents (Codex, Amp, Aider, etc.).