Slash Command

/spec

Biases HarnessFlow workflow toward spec authoring or revision via hf-specify skill. Router validates upstream preconditions before producing spec artifact with EARS/BDD/MoSCoW/INVEST formats.

documentation

developer-tools

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

Details

Namespacecommands/

Prompt Preview

Bias toward the HarnessFlow `hf-specify` skill, but **do not bypass the router**.

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 "spec authoring or revision".
3. The router decides:
   - if upstream discovery / discovery-review preconditions are not satisfied, it routes back to `hf-product-discovery` or `hf-discovery-review` first,
   - if they are satisfied, it routes into `skills/hf-specify/SKILL.md`.
4. Follow `hf-specify`'s own SKILL.md (EARS / BDD / MoSCoW / INVEST / ISO 25010 ...

Command Content

Other plugins with /spec

/specs

Generates collaborative specifications for a feature, producing Intent, BDD scenarios, architecture notes, and acceptance criteria.

agentic-dev-team

/specify

242

Transforms project briefs into structured specifications with functional requirements, acceptance criteria, and testable requirements. Generates docs/specification.md and optionally auto-proceeds to planning.

attune

/spec

3.2k

Authors structured NLSpec from natural language description using multi-AI research, with adversarial completeness validation, scoring, and saved spec file.

octo

/spec

Generates or refines Choo Choo Ralph spec files (.choo-choo-ralph/*.spec.md) from plan files or conversation context, using parallel sub-agents for codebase and tech research.

choo-choo-ralph

/spec

27.2k

Starts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.

agent-skills

/spec

1.4k

Generates complete feature specifications from a feature name or rough idea, spanning requirements to implementation plan.

kiro-skill

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-specify` skill, but **do not bypass the router**. 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 "spec authoring or revision". 3. The router decides: - if upstream discovery / discovery-review preconditions are not satisfied, it routes back to `hf-product-discovery` or `hf-discovery-review` first, - if they are satisfied, it routes into `skills/hf-specify/SKILL.md`. 4. Follow `hf-specify`'s own SKILL.md (EARS / BDD / MoSCoW / INVEST / ISO 25010 ...

Bias toward the HarnessFlow hf-specify skill, but do not bypass the router.

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 "spec authoring or revision".
The router decides:
- if upstream discovery / discovery-review preconditions are not satisfied, it routes back to hf-product-discovery or hf-discovery-review first,
- if they are satisfied, it routes into skills/hf-specify/SKILL.md.
Follow hf-specify's own SKILL.md (EARS / BDD / MoSCoW / INVEST / ISO 25010 / QAS / Success Metrics) to produce the spec artifact.

Hard rule: this command is a bias, not a bypass. Workflow position is decided by on-disk artifacts, not by the command name.

The user request following this command is the spec topic / revision intent.