By citadelgrad
Plan, build, and swarm beads epics - sequential and parallel epic execution with CE code review (2 agents, 3 commands)
Use this agent to plan complete features from initial concept through implementation-ready beads tasks. Orchestrates research, documentation, and task breakdown with approval gates. <example> Context: User describes a substantial new feature or system they want to build user: "I want to build an automated error-fixing system that monitors GlitchTip, uses AI to propose fixes, and lets me approve patches before creating PRs" assistant: "This is a significant feature that would benefit from structured planning. Let me use the epic-planner agent to research approaches, create PRD and SPEC documents, and break this down into implementable tasks." <commentary> The epic-planner triggers because the user is describing a new feature that requires research, documentation, and task decomposition - not a simple implementation request. </commentary> </example> <example> Context: User wants to plan a feature but hasn't provided full details user: "Help me plan out a notification system for the app" assistant: "I'll use the epic-planner agent to research notification system approaches, document requirements, and create a structured implementation plan with beads tasks." <commentary> Even with limited initial details, epic-planner is appropriate because it will conduct research and gather requirements through the planning process. </commentary> </example> <example> Context: User explicitly requests planning workflow user: "I need you to create a PRD and SPEC for user authentication, then break it into tasks" assistant: "I'll use the epic-planner agent to create the PRD and SPEC documents with approval gates, then decompose them into granular beads tasks." <commentary> User explicitly requested the PRD/SPEC/tasks workflow that epic-planner provides. </commentary> </example>
Orchestrates complete feature development from epic to deployment. Manages architecture review, implementation, quality gates, and validation using beads for task tracking.
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.
Modular Claude Code plugin suite for productive development. The core plugin provides 10 slash commands, 8 specialized AI agents, and 4 skills. Specialized sub-plugins add beads epic workflows, browser automation, mutation testing, and more.
# Install from the plugins marketplace
/plugin marketplace add citadelgrad/scott-cc
Or browse the marketplace at https://claudecode.dev/plugins to discover this and other plugins.
/scott-cc:new-task - Analyze task complexity and create implementation plan/scott-cc:code-explain - Generate detailed explanations/scott-cc:code-optimize - Performance optimization/scott-cc:code-cleanup - Refactoring and cleanup/scott-cc:lint - Linting and fixes/scott-cc:docs-generate - Documentation generation/scott-cc:component-new - Create React components/scott-cc:page-new - Create Next.js pages/scott-cc:security-cheatsheet - Comprehensive security reference/scott-cc:gha - Debug failing GitHub Actions runs and audit workflow YAMLStop event) - Ghostty terminal tab indicator when Claude finishes responding
Install these sub-plugins from the marketplace for additional capabilities:
The beads-epic-builder plugin provides three ways to work with beads epics:
The epic-planner agent guides features from concept to implementation-ready tasks:
User describes feature
|
v
Research (adaptive depth)
|
v
Research Approval Gate
|
v
Create PRD Document
|
v
Create SPEC Document
|
v
Document Approval Gate
|
v
Create Beads Epic + Tasks
/build-feature <epic-id>The feature-builder agent implements tasks one at a time through 6 phases:
/build-feature <epic-id> [--resume]
|
v
Phase 1: Epic Setup (verify, test requirements audit)
Phase 2: Architecture Review (conditional agent spawning)
Phase 3: Implementation (task-by-task via beads)
Phase 4: Quality Review (DRY/KISS via simplifier skills)
Phase 5: Validation (tests, lint, types, security)
Phase 6: Final Review (commit, close epic)
Each phase writes a checkpoint for --resume support.
/epic-swarm <epic-id>Spawns parallel worker agents in isolated git worktrees:
/epic-swarm <epic-id> [--max-parallel 3] [--no-review] [--dry-run]
|
v
Phase 1: Load epic, build dependency-aware wave plan
Phase 2: Execute waves (parallel workers in worktrees)
- Wave 1: independent tasks run simultaneously
- Wave 2: tasks depending on Wave 1
- Wave N: continue until done
- Merge branches, run tests, close tasks after each wave
Phase 3: CE code review (architecture, simplicity, security, performance)
Phase 4: Ship (commit, push)
Checkpointing after every wave survives context compaction.
Security-focused development with security advisory and vulnerability scanning agents
Comprehensive mutation testing for identifying zombie tests and improving test quality through automated code mutation analysis and parallel test execution
Performance engineering and optimization with bottleneck analysis and performance profiling
Deep research, learning, and technical writing tools with AI writing pattern detection
Complete browser testing & validation suite with E2E test generation, browser automation, and UI validation
npx claudepluginhub citadelgrad/scott-cc --plugin beads-epic-builderOrchestrate full delivery of a beads epic through polecats, refinery, and integration branches. The final stage of the design-to-delivery pipeline: gt-toolkit formulas produce the spec and plan, design-to-beads converts the plan into beads issues, and this skill delivers those issues through Gas Town infrastructure.
SAGA - Structured Autonomous Goal Achievement: epic/story workflow with autonomous execution
Plan-only mode and GitHub-issue-to-Beads workflow. Provides planning without auto-execution and structured work decomposition into Beads epics, tasks, and sub-tasks with verifiable acceptance criteria.
Autonomous GitHub Project Management workflow with orchestrator-agent coordination for parallel task execution via git worktrees
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
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.).