traceflow

What problem does it solve?

Software projects accumulate documentation drift as ideas evolve into domain knowledge, architectural decisions get made, and implementation specs ship. Without enforced traceability, it becomes impossible to answer which spec owns a file, why a business rule exists, or which ADR ratified a structural choice. traceflow solves this by treating documentation as a first-class, lifecycle-governed artifact with mandatory delta tracking and reverse-index navigation.

Core Features & Use Cases

• Four artifact axes: Explicitly governs ideas (brainstorms), domain (durable knowledge), decisions (append-only ADRs), and specs (implementation slices) through defined state machines and promotion criteria.
• Spec-delta traceability: Every spec declares exactly which domain files and ADRs it adds, modifies, or removes, with typed NONE justifications for non-domain work like refactors or hotfixes.
• Behavior-scoped diagrams: First-class diagram convention under the domain axis, featuring reusable fragments with canonical ownership, anchor-based cross-references, and composite rollups for scenario navigation.
• Use Case: A Go monorepo with multiple bounded contexts uses traceflow to keep business rules, architectural decisions, and implementation slices synchronized, run structural invariants via bash smoke tests, and rebuild file-path maps automatically.

Quick Start

Use the traceflow skill to govern your project documentation lifecycle by promoting ideas to domain knowledge, ratifying ADRs, and scaffolding implementation specs with mandatory delta tracking.