Slash Command

/build

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.

testing

code-quality

npx claudepluginhub hujianbest/harness-flow --plugin harness-flow

Details

Namespacecommands/

Prompt Preview

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...

Command Content

Other plugins with /build

/build

Implements 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.

/build

Executes 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.

godmode

/implement

Implements feature tasks from design spec using TDD and existing codebase patterns. Accepts feature name with optional --task number and --auto mode.

sddw

/devkit.task-implementation

174

inherit9 tools

developer-kit

/execute-task

172

Implements a single development task from a specified task file by analyzing requirements, mirroring code patterns, validating acceptance criteria, running quality checks, and marking completion.

/build

27.2k

Implements next planned task incrementally via TDD: write failing test, minimal implementation, full tests/build verification, commit changes.

agent-skills

Stats

Stars30

Forks13

Last CommitApr 29, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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:

Enter via skills/using-hf-workflow/SKILL.md and hand off to skills/hf-workflow-router/SKILL.md.
Tell the router that the user's intent is "implement the current active task".
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.
If preconditions hold, the router routes into skills/hf-test-driven-dev/SKILL.md.
If preconditions do not hold, the router routes back to the upstream node (e.g. hf-tasks, hf-design-review) instead of starting implementation.

Hard rules carried by hf-test-driven-dev:

Canon TDD: write the test design first, RED must exist before GREEN.
Walking Skeleton + Two Hats discipline; opportunistic / preparatory refactoring inside the same node.
Fresh Evidence Principle: RED / GREEN evidence must be re-captured for the current run.
Clean Architecture conformance check is part of the node, not deferred to review.

The user request following this command is optional implementation hint or scope reminder. The router does not need it to identify the active task.