FIT Workflows
FIT runs nine custom Archon workflows across three repos. Each is a deterministic DAG — a YAML file that specifies nodes, dependencies, models, allowed tools, and gating conditions. The methodology is PRP/PIV (see PRP Workflow); these are the executable expressions of it.
For the visual catalog with Archon-style cards, see /workflows/.
The catalog
Section titled “The catalog”| Workflow | Repo | Category | When to use | Does | Not for |
|---|---|---|---|---|---|
| fit-create-issue | Archon | Development | Report a reproducible bug as a GitHub issue | Classifies against the FIT stack, gathers context in parallel, reproduces, gates on success, creates a structured issue with evidence | Features, enhancements, non-bug work |
| fit-fix-issue | Archon | Development · Code Review | Default issue-fix (~80% of work, Sonnet 4.6) | Ten-phase DAG: classify → research → investigate/plan → implement → validate → draft PR → review → self-fix → simplify → report | Architectural changes (use Pro), comprehensive reviews, CI failures |
| fit-fix-issue-pro | Archon | Development · Code Review | Heavyweight issue-fix (~20% of work, Opus 4.6) | Same ten-phase DAG, pinned to Opus 4.6 for deeper reasoning on architectural and governance-graph work | Trivial fixes (use the non-Pro), comprehensive reviews |
| fit-n8n-env-audit | Archon | CI-CD | Audit n8n env config for a FIT repo | Runs the deterministic n8n-env-audit script, writes JSON + markdown artifacts; read-only | Mutating config, fixing findings, non-n8n environments |
| fit-repo-overview | Archon | CI-CD | Cross-repo status dashboard | Collects branch / worktree / issue / PR / divergence data via gh + git, renders a scannable markdown dashboard | Modifying repo state, closing PRs, deep-dives |
| fit-blog-publish | fit-blog | Automation | Draft and publish a blog post (on-demand or weekly) | Fifteen-step pipeline: classify → plan → voice calibrate → topic → image gen → draft → validate → commit for human push | Editing existing posts, publishing without human review |
| n8n-builder-demo-task | n8n-builder | Development | Repo task against the demo n8n env | Pins to demo, validates credentials, 8-iteration loop with strict env isolation, lifecycle precheck, persists report | Dev or prod env tasks, cross-environment changes |
| n8n-builder-dev-task | n8n-builder | Development | Repo task against the dev n8n env (standard) | Pins to dev, validates credentials, 8-iteration loop with strict env isolation, lifecycle precheck, persists report | Demo or prod env tasks, cross-environment changes |
| n8n-builder-prod-task | n8n-builder | Development | Repo task against the prod n8n env (rare) | Pins to prod, runs a read-only safety check first, 8-iteration loop with conservative validation, persists report | Demo or dev env tasks, exploratory work |
Architecture notes
Section titled “Architecture notes”- Workflows live in their repos’
.archon/workflows/directories. Five FIT-shared workflows live underArchon/.archon/workflows/fit/. Two repo-specific lanes live infit-blogandn8n-builder. - The PRP/PIV methodology (PRP Workflow) defines the pattern. The workflows above are instances.
- Cards on
/workflows/render from the sameworkflows.yamldata file. Update the YAML, both surfaces update.