skills.rest
gaberger
gabergerCOMMUNITY
Explore all skills by this author →
GitHub

workplan-format

Define a canonical workplan schema for HexFlo swarm planning and execution.

4|Updated Mar 16, 2026
Search Tags:#planning#adr#swarm#tasks#phases#workplan#hexflo
One-click install
npx skills add https://github.com/gaberger/hex --skill workplan-format
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workplan-format
Source: https://github.com/gaberger/hex/tree/main/.claude/skills/workplan-format
Command: npx skills add https://github.com/gaberger/hex --skill workplan-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical workplan schema standardizes HexFlo swarm planning and execution across teams.

Core Features & Use Cases

  • Canonical workplan schema and lifecycle (phases, tasks, gates) for HexFlo swarms.
  • ADR-050 pipeline integration ensuring workplans are associated with ADRs and traceable.
  • Guidance for planning, execution, and reconciliation of swarm work.

Quick Start

Create a workplan that decomposes a feature into phased tasks using the canonical schema.

Frequently Asked Questions about workplan-format

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

FAQPage Schema
How do I structure a workplan for HexFlo swarm planning?▼

Apply a canonical workplan schema to decompose features into ordered phases and tasks. The schema enforces required fields, lifecycle gates, and traceable relationships to standardize HexFlo swarm execution.

What are workplan gates and how do they guide task execution?▼

Gates are lifecycle checkpoints within the workplan schema that guide swarm task execution. They enforce an ordered progression, ensuring phase prerequisites are met before subsequent tasks begin.

How do ADR references integrate into HexFlo workplans?▼

ADR references integrate into HexFlo workplans via ADR-050 pipeline rules, ensuring features remain associated with architectural decisions to keep swarm planning and execution fully traceable.

Does the workplan schema require structured JSON output for tooling?▼

Yes, the workplan schema requires structured JSON output. This standardized format is consumed directly by HexFlo tooling to automate and track swarm planning alongside execution.

What is the best way to decompose a feature into phased tasks?▼

The best way is applying the canonical workplan schema, which breaks features into ordered phases and tasks. It enforces lifecycle gates, ADR references, and traceable relationships for clear execution.

When do I need a canonical workplan schema for swarm tasks?▼

You need a canonical workplan schema when standardizing HexFlo swarm planning across teams. It enforces required fields and structured JSON output to maintain consistent execution and traceability.

Related Skills

Explore More Software Engineering Skills→
imvanzenimvanzen

technical-context-discovery

Inspect repository rules and analyze codebase patterns before code changes.

Community
Advanced
gabergergaberger
4

hex-swarm

Coordinate HexFlo swarms to manage multi-agent development tasks across adapters and lifecycle actions.

Community
Advanced
gabergergaberger
4

hex-workplan

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

Community
Advanced
vuralserhat86vuralserhat86
43

github_project_automation

Automate GitHub issue creation, project board synchronization, and sprint planning.

Community
Advanced