Harness Workflow — Agent Skill for requirement-to-delivery pipeline.
hx is an Agent Skill invoked via /hx <command> that orchestrates the full requirement-to-delivery pipeline.
Runtime config files:
.hx/config.yaml— single-project config.hx/workspace.yaml— workspace root config (multi-project).hx/rules/*.md— project rules.hx/hooks/— custom hooks (optional).hx/pipelines/— custom pipelines (optional)
npx skills add hxflow/workflowAfter installation, run /hx init in your project to initialize.
/hx go feature-name # full pipeline
/hx doc feature-name # gather requirements
/hx plan feature-name # generate plan
/hx run feature-name # execute tasks
/hx check feature-name # quality check
/hx mr feature-name # create MR
/hx reset feature-name [plan|doc|code]
| Command | Phase | Description |
|---|---|---|
go |
Full | Full pipeline: doc → plan → run → check → mr |
doc |
Phase 01 | Gather requirements and create requirement doc |
plan |
Phase 02 | Generate execution plan and progress.json |
run |
Phase 04 | Execute tasks |
check |
Phase 06 | Quality gate (review, gates, engineering hygiene) |
mr |
Phase 08 | Create Merge Request |
init |
Init | Generate config file and rule templates |
status |
Status | View task progress |
reset |
Maintenance | Reset doc, plan, or code state |
hxflow/
SKILL.md # Skill entry point
commands/hx-*.md # Command contracts
scripts/tools/*.ts # Fact-fetching scripts (structured data for AI)
templates/ # Rule templates
The installed skill entry is hxflow/SKILL.md. It routes /hx <command> to the
matching command contract, resolves hooks first, and asks the agent to read only
the files needed for the current command.
Project scaffold:
.hx/
config.yaml # single-project mode
workspace.yaml # multi-project (workspace) mode
rules/
requirement-template.md
plan-template.md
bugfix-requirement-template.md
bugfix-plan-template.md
hooks/ # optional
pipelines/ # optional
hx-init copies rule templates into .hx/rules/ and registers them in config.yaml (or workspace.yaml) under rules.templates; the runtime reads only from config.
Long-running work can continue in background agent or shell sessions. Use
list_agents and read_agent to inspect agent work, and write_agent only when
an idle agent is waiting for more input. Use list_bash, read_bash, and
write_bash for shell sessions; keep the two session types separate.
When the repo contains multiple sub-services, hx-init scans candidates and generates .hx/workspace.yaml:
- Root
workspace.yamlholds the coordination layer:paths,gates,runtime,rules.templates,projects - Sub-projects can have their own
config.yamlto override onlycwd,src, and gates; everything else inherits from workspace - Requirement and plan docs are maintained at the workspace root; task-level changes are scoped to the target service
- Commands resolve the target project from the task's
cwd, then merge workspace and project config by priority
- Bun >= 1.0.0; fall back to
npx tsxif Bun is not available
bun run hx:test # full regression
bun run hx:test:unit # unit tests
bun run hx:test:integration # integration tests- Repo:
https://github.com/hxflow/workflow - npm registry:
https://npm.pkg.github.com(@hxflowscope) - Push a
v*tag to trigger automated release - Provide
NODE_AUTH_TOKENfor local publish
Built-in agent evals scaffold at hxflow/evals/:
datasets/core.jsonl— core pipeline samplesdatasets/edge.jsonl— edge casesdatasets/regressions.jsonl— historical regression casesruns/history.json— trend history
bun run hx:evals:validate
bun hxflow/scripts/lib/evals.ts score tests/fixtures/evals/sample-results.json --write-run /tmp/hx-eval-run.json --record
bun run hx:evals:report
bun hxflow/scripts/lib/evals.ts extract-failures /tmp/hx-eval-run.json --output /tmp/hx-eval-candidates.jsonlMIT