hex-workplan

Create, validate, and manage hex workplans and behavioral specs for HexFlo.

4|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/gaberger/hex --skill hex-workplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hex-workplan
Source: https://github.com/gaberger/hex/tree/main/.claude/skills/hex-workplan
Command: npx skills add https://github.com/gaberger/hex --skill hex-workplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create, validate, and manage hex workplans and behavioral specs to drive feature development with traceability between requirements and implementation.

Core Features & Use Cases

  • Two artifacts are required before code begins: Behavioral Specs → docs/specs/<feature>.json and Workplan → docs/workplans/feat-<feature>.json.
  • Specs provide behavior expectations; Workplans map tasks to adapters, tiers, and dependencies, enabling traceability and reproducible execution.
  • HexFlo executes workplans by dispatching agents per step and validating outcomes against the plan.

Quick Start

Define your feature by writing behavioral specs, then generate and validate a corresponding workplan with the hex-workplan tooling.

Frequently Asked Questions about hex-workplan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure traceability between behavioral specs and feature implementation?

Behavioral specs and workplans ensure traceability by mapping tasks to adapters, tiers, and dependencies. You create two artifacts before coding: specs in docs/specs/ and workplans in docs/workplans/, enabling strict spec-workplan alignment for end-to-end delivery.

What is a two-artifact workflow for feature planning?

A two-artifact workflow requires generating a behavioral spec JSON and a workplan JSON before code begins. Specs define behavior expectations, while workplans orchestrate task execution and dependency mapping for reproducible delivery.

How do I create a structured workplan for feature development?

To create a structured workplan, define your feature's behavioral expectations first, then generate a corresponding workplan JSON file. This workplan maps tasks to adapters and dependencies, applying tiered execution validation to ensure reproducible outcomes.

Does feature planning require strict spec-workplan alignment?

Yes, strict spec-workplan alignment is enforced. The workflow requires both a behavioral spec and a workplan to be created and validated before implementation begins, ensuring all execution steps map directly to documented behavior expectations.

How does tiered execution validation work for project management workplans?

Tiered execution validation dispatches agents per workplan step and validates outcomes against the plan. It checks task completion against mapped adapters and dependencies, ensuring reproducible execution and strict alignment with the original spec.