By markshust
Orchestrate autonomous TDD-driven feature development: generate structured plans with task breakdowns and dependencies, execute them in parallel using Red-Green-Refactor worker agents, critically review architecture for gaps, configure projects for TDD, and enforce coding/testing standards across file batches.
Devil's advocate architectural reviewer. Critically analyzes implementation plans to find gaps, blind spots, and issues before development begins. Auto-applies Critical and Important fixes to plan files.
Code standards enforcement worker. Reviews and fixes a batch of files to match project coding standards without changing behavior.
TDD implementation worker. Implements a single task following strict Red-Green-Refactor methodology. Use for executing individual plan tasks autonomously.
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users should be able to X, Y, Z"), vague-noun patterns ("a system for", "a way to", "an app that", "functionality for"), and explicit build verbs ("build", "create", "add a feature", "help me implement", "I need to build"). Do NOT use this for "implement the plan" or "run the plan" - those should use plan-orchestrate instead. Skip for quick bug fixes, single-line changes, questions, or documentation.
Execute implementation plans with parallel TDD workers. Use when ready to run, execute, or start a plan. Triggers on "run the plan", "execute the plan", "implement the plan", "start the plan", "start implementation", "orchestrate", "begin autonomous execution". Requires a plan created by plan-create.
One-time interactive setup to configure a project for autonomous development. Use when setting up a new project for TDD-based autonomous development with HCF.
Update project configuration to match the latest HCF plugin defaults. Use when the HCF plugin has been updated and you want to sync your project's config.
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.
Autonomous development plugin for Claude Code. Define requirements with a PM, then let parallel workers implement everything using TDD.
HCF separates planning (human-in-the-loop) from execution (fully autonomous):
Planning → Human + AI collaborate on requirements
Execution → Parallel TDD workers implement autonomously
Add the marketplace, install, then reload:
/plugin marketplace add markshust/hcf
/plugin install hcf@hcf
/reload-plugins
/project-setup
Interactively configures your project:
.claude/ config directoryJust describe what you want:
"Help me implement user authentication with JWT"
The plan-create skill activates automatically to:
feature/{plan-name} branch for the work.claude/plans/user-auth/ with task filesAfter planning completes, you'll be asked:
Ready to begin autonomous implementation?
- Yes, start now
- No, I'll run it later
If you chose "later" or want to re-run, say:
"Run the user-auth plan" or "Execute the plan"
The plan-orchestrate skill auto-triggers. It verifies you're on the correct feature/{plan-name} branch before starting, and automatically uses ralph-wiggum for session persistence if installed. If not installed, you'll see a warning but execution continues.
After completion, you'll be prompted to push the branch and create a PR (never done without your permission).
ralph-wiggum is prompted during /project-setup, or install manually:
/plugin marketplace add anthropics/claude-code
/plugin install ralph-wiggum@claude-code-plugins
| Phase | Type | What Happens |
|---|---|---|
| Setup | One-time | Configure project for autonomous dev |
| Planning | Interactive | Discover codebase, brainstorm scope, then define tasks with human guidance |
| Post-Plan Pipeline | Automated | Configurable agents review the plan |
| Execution | Autonomous | Parallel TDD implementation + post-implementation pipeline |
The pipeline system controls which agents run before and after the core TDD implementation. It's configured in .claude/pipeline.md:
# Pipeline
## post-plan
- devils-advocate
## post-implementation
<!-- - standards-enforcer -->
Phases:
| Phase | When | Default Agent |
|---|---|---|
post-plan | After plan creation, before user review | devils-advocate |
post-implementation | After all TDD workers complete, before commit | none (standards-enforcer available, off by default) |
Customizing the pipeline:
Add, remove, or reorder agents at any phase. For example, to add a custom security-reviewer to post-plan, enable the built-in standards-enforcer (off by default), and add a custom doc-updater to post-implementation:
# Pipeline
## post-plan
- devils-advocate
- security-reviewer
## post-implementation
- standards-enforcer
- doc-updater
Creating custom agents:
Create a markdown file in your project's .claude/agents/ directory:
.claude/agents/doc-updater.md
The agent file follows the standard Claude Code agent format with frontmatter:
---
name: doc-updater
description: "Updates documentation when implementation changes."
model: sonnet
tools: Read, Edit, Glob, Grep
---
You are a documentation updater. Your job is to...
{define the agent's behavior, process, and output format}
npx claudepluginhub markshust/hcf --plugin hcfPersona-driven AI development team: orchestrator, team agents, review agents, skills, slash commands, and advisory hooks for Claude Code
Implement code from /deep-plan sections with TDD, code review, and git workflow
A TDD-driven iterative feedback loop for software development with Claude Code. 16 cohesive skills + 2 custom subagents walk an idea from brainstorm → plan → execute → tdd → iterate, with checkpoints throughout. Vertical-slice TDD, parallel coder/overseer review, no auto-commits. Single entry point: 'let's evanflow this'.
Long-running agent harness with 5-layer memory architecture, GitHub integration, autonomous batch processing, Agent Teams with ATDD, 9 hooks (safety, quality gates, team coordination), and 6 Agent Skills
Opinionated 5-phase development lifecycle for Claude Code — language-agnostic, repo-local bin/* delegation
Test-driven development methodology with red-green-refactor cycles and code review