HCF plugin
HCF separates planning with a human from autonomous execution: parallel workers implement the plan using TDD.
- 84 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The execution phase is autonomous: parallel workers change code and create branches without confirming each step.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/hcfDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The execution phase is autonomous: parallel workers change code and create branches without confirming each step.
This is third-party code. Review the repository files before installing.
What it does
HCF is a Claude Code plugin that splits work into four phases: project setup, interactive planning, automatic plan review and autonomous execution. The `/project-setup` command detects the stack and creates a `.claude/` directory. The `plan-create` skill triggers on phrases like "Help me implement", asks clarifying questions, breaks the task into subtasks with dependencies, writes requirements as test descriptions and creates a `feature/{plan-name}` branch. The `plan-orchestrate` skill runs parallel workers that implement tasks using TDD according to the dependency graph. `project-update` syncs configuration, and agents can be enrolled at hooks such as `post-plan`.
Who it is for. Claude Code developers ready to refine requirements with an assistant and hand implementation to parallel workers with tests.
Good fit when
- A feature is first broken into tasks and tests, then implemented without intervention.
- Planning must stay with a human while execution goes to agents.
- Independent plan tasks should run in parallel.
- A new project needs one time setup of stack, tests and linter.
Not a fit when
- The task is small and a plan with workers would only slow it down.
- Agents must not change code without manual review of each step.
- The project cannot be covered by automated tests.
Example request
Help me implement JWT user login: ask clarifying questions first, then write a plan and start parallel execution.Limitations
Execution is fully autonomous: parallel workers edit code and create a branch, so run it on a separate branch and review the result before merging. Quality depends on the plan and test coverage. The plugin targets Claude Code and installs through `/plugin marketplace add`, after which `/reload-plugins` is needed. Configuration lives in `.claude/` and the plans directory can be changed. The plugin does not replace human code review: check the diff and test results before merging.
How to disable. Run `/plugin uninstall hcf@hcf` and delete the `.claude/plans/` directories and settings created by `/project-setup`. Close the `feature/{plan-name}` branch by hand.
FAQ
Which skills are included?
`project-setup`, `project-update`, `plan-create` and `plan-orchestrate`. Any can be invoked as `/skill-name`.
When does `plan-orchestrate` trigger?
Automatically on phrases like "Run the plan" or "Start implementation", or with `/plan-orchestrate [plan-name]`.
How are planning questions divided?
Into must answer ones and ones that fall back to a default if you stay silent.
What is created in the project?
A `.claude/` directory with settings and `.claude/plans/<name>/` with task files. The plans directory can be changed.
What are plan hooks?
Points where agents plug in, for example `post-plan` for reviewing the plan before execution.
Discussion
No questions or reviews yet.
Related
PluginsClaude Code plugin with 17 skills: task sizing, design review, TDD, fresh-context subagents and a PR after three human decisions.
A Claude Code plugin links planning, implementation and task checks, retains progress and controls how independently agents work.
A plugin that turns Claude Code into a 16 agent team: documentation first planning, TDD and 9 pre-merge quality gates.
A Claude Code skill that drives a hard task through explore, plan, execute and reflect, writing every decision to disk.
Hooks and skills make Claude Code plan before coding, test before shipping and escalate when it is not confident.
Codely team skills that run agent work in phases: a plan in a file or GitHub issues, review after each phase and a clean commit
README in short
An autonomous development plugin for Claude Code: planning with a human, plan review by agents and parallel TDD execution respecting dependencies.