Technical Workflow System

A structured pipeline for turning ideas into verified production code. Four work types — Feature, Bugfix, Epic, and Cross-cutting — each follow their own pipeline through phases of exploration, decisions, and validated specifications. Features, bugfixes, and epics continue through implementation planning, test-driven development, and final review. Cross-cutting concerns are terminal at specification.

Run /workflow-start to see all active work, or /start-feature, /start-bugfix, /start-epic, /start-cross-cutting to begin.
Layer 1 — Unified Entry
/workflow-start
Discover all active work, route to start or continue
Layer 2 — Work-type Entry
/start-feature
New feature
/start-bugfix
New bugfix
/start-epic
New epic
/start-cross-cutting
New cross-cutting concern
/continue-feature
/continue-bugfix
/continue-epic
/continue-cross-cutting
Layer 3–4 — Phase Pipeline
Feature
Research
optional
Discussion
Bugfix
Investigation
Epic
Research
Discussion
multi-topic
Cross-cutting
Research
optional
Discussion
Specification
terminal
Convergence — Feature / Bugfix / Epic
S
Specification
Build validated specifications — filter hallucinations, enrich gaps
skillworkflow-specification-process
P
Planning
Transform specs into phased plans with tasks and acceptance criteria
skillworkflow-planning-process
I
Implementation
Execute plan via agent-based TDD — executor and reviewer per task
skillworkflow-implementation-process
R
Review
Verify implementation against plan using parallel verification agents
skillworkflow-review-process
GitHub