Workflows
Overview
Section titled “Overview”Each instruction tool maps to a detailed workflow specification describing trigger conditions, required skills, decision points, and success chains. The workflows are described using finite state machine (FSM) diagrams and execution sequence diagrams.
Workflow Index
Section titled “Workflow Index”| # | Workflow | Instruction Tool | Key Skills | Success Chains |
|---|---|---|---|---|
| 00 | Meta-Routing | meta-routing | scope-clarification, ambiguity-detection | Terminal node |
| 01 | Bootstrap | task-bootstrap | req-analysis, req-scope | design, implement, research, + 9 more |
| 03 | Design | system-design | arch-system, arch-security | feature-implement, policy-govern |
| 04 | Plan | strategy-plan | strat-roadmap, strat-prioritisation | feature-implement, enterprise-strategy |
| 05 | Implement | feature-implement | req-analysis, arch-system | test-verify, code-review |
| 06 | Physics Analysis | physics-analysis | qm-, gr- | code-review, feature-implement |
| 07 | Evaluate | quality-evaluate | eval-output-grading, bench-blind-comparison | prompt-engineering, code-refactor |
| 08 | Review | code-review | qual-review, qual-security | policy-govern, code-refactor |
| 09 | Testing | test-verify | qual-code-analysis, bench-eval-suite | code-review, issue-debug |
| 10 | Debug | issue-debug | debug-assistant, debug-root-cause | test-verify, code-refactor |
| 11 | Refactor | code-refactor | qual-refactoring-priority, gr-geodesic-refactor | test-verify, code-review |
| 12 | Adapt | routing-adapt | adapt-aco-router, adapt-hebbian-router | agent-orchestrate, quality-evaluate |
| 13 | Document | docs-generate | doc-readme, doc-api, doc-runbook | code-review, enterprise-strategy |
| 14 | Enterprise | enterprise-strategy | lead-transformation-roadmap, lead-capability-mapping | policy-govern, system-design |
| 15 | Govern | policy-govern | gov-prompt-injection-hardening, gov-workflow-compliance | code-review, fault-resilience |
| 16 | Orchestrate | agent-orchestrate | orch-agent-orchestrator, orch-result-synthesis | quality-evaluate, fault-resilience |
| 17 | Prompt Engineering | prompt-engineering | prompt-engineering, prompt-refinement | quality-evaluate, policy-govern |
| 18 | Research | evidence-research | synth-research, synth-engine | strategy-plan, system-design |
| 19 | Resilience | fault-resilience | resil-homeostatic, resil-redundant-voter | policy-govern, quality-evaluate |
| 20 | Onboard Project | project-onboard | — | Terminal node |
Routing Architecture
Section titled “Routing Architecture”The meta-routing workflow is the universal entry point. It classifies every incoming request and dispatches to the appropriate instruction tool:
flowchart TD
Request([User Request])
Meta[meta-routing]
Bootstrap[task-bootstrap]
Design[system-design]
Implement[feature-implement]
Research[evidence-research]
Review[code-review]
Debug[issue-debug]
Plan[strategy-plan]
Other[... 14 more tools]
Request --> Meta
Meta -->|unclear scope| Bootstrap
Meta -->|architecture| Design
Meta -->|build feature| Implement
Meta -->|gather info| Research
Meta -->|code review| Review
Meta -->|something broken| Debug
Meta -->|plan/roadmap| Plan
Meta -->|specialist| Other
Bootstrap -->|scope locked| Design
Bootstrap -->|scope locked| Implement
Bootstrap -->|scope locked| Research
FSM Conventions
Section titled “FSM Conventions”All workflow FSMs use stateDiagram-v2 (Mermaid). States represent cognitive phases; transitions show conditions that move execution forward or back.
Common re-entry transitions (backward arrows) represent:
- Reflective interruption — quality check reveals insufficient output
- Scope revision — new information changes requirements
- Model escalation — cheap model cannot resolve; escalate to strong