From harness-flow
Implements the current active HarnessFlow task using TDD with fresh evidence via hf-test-driven-dev. Requires exactly one locked Current Active Task and met preconditions.
How this command is triggered — by the user, by Claude, or both
Slash command
/harness-flow:buildThe summary Claude sees in its command listing — used to decide when to auto-load this command
Bias toward the HarnessFlow `hf-test-driven-dev` skill. Steps: 1. Enter via `skills/using-hf-workflow/SKILL.md` and hand off to `skills/hf-workflow-router/SKILL.md`. 2. Tell the router that the user's intent is "implement the current active task". 3. The router checks preconditions: - exactly one `Current Active Task` is locked, - upstream design / tasks / approvals are in place, - no blocking gate is open against this task. 4. If preconditions hold, the router routes into `skills/hf-test-driven-dev/SKILL.md`. 5. If preconditions do not hold, the router routes back to the upstrea...
Bias toward the HarnessFlow hf-test-driven-dev skill.
Steps:
skills/using-hf-workflow/SKILL.md and hand off to skills/hf-workflow-router/SKILL.md.Current Active Task is locked,skills/hf-test-driven-dev/SKILL.md.hf-tasks, hf-design-review) instead of starting implementation.Hard rules carried by hf-test-driven-dev:
The user request following this command is optional implementation hint or scope reminder. The router does not need it to identify the active task.
npx claudepluginhub hujianbest/harness-flow --plugin harness-flow/buildImplements features using TDD workflow: write failing tests, add minimal passing code, refactor, commit; verifies via quality gates including static analysis, security scan, and coverage checks.
/auto-implement-tasksIntelligently implements tasks with context analysis, code generation, tests, progressive steps, QA checks, and post-implementation deliverables like PR descriptions.
/buildImplements an approved plan task by task using TDD with graduated quality gates, then chains into review and check stages. Resumes interrupted builds from checkpoint.
/buildExecutes implementation plan from docs/plans/ using TDD (RED-GREEN-REFACTOR), parallel agents for independent tasks, and 2-stage code reviews. Produces code, tests, atomic git commits, and review reports.
/implementImplements feature tasks from design spec using TDD and existing codebase patterns. Accepts feature name with optional --task number and --auto mode.
/devkit.task-implementationImplements a specific task from a spec-generated task list via structured workflow including git checks, implementation, verification, and todo updates. Requires --task=name; optional --lang=java|spring|typescript|nestjs|react|python|general.