Govern software documentation lifecycle with mandatory spec-delta traceability and append-only ADRs.
npx skills add https://github.com/trypanic/skills --skill traceflow
Please help me install this Agent Skill. Skill: traceflow Source: https://github.com/trypanic/skills/tree/main/traceflow Command: npx skills add https://github.com/trypanic/skills --skill traceflow
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.
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.
High-intent search queries and answers about installing and using this skill.
Documentation traceability is maintained by enforcing spec-delta tracking, where every spec declares exact additions, modifications, or removals to domain files and ADRs. This structure ensures synchronized business rules and implementation slices across multi-area monorepos.
Managing ADRs alongside specs requires an append-only decision log mapped to implementation artifacts. Governing the lifecycle across four axes—ideas, domain, decisions, and specs—ensures every structural choice is ratified and linked to its corresponding spec.
Tracking file ownership relies on structural invariants and a file-path reverse-index map. This automatically rebuilds the link between any file and its owning spec, preventing documentation drift and clarifying ownership across teams.
Lifecycle-driven documentation applies to refactors and hotfixes through typed NONE justifications. When a spec does not modify domain files, it explicitly declares a NONE delta type, maintaining strict traceability without forcing irrelevant domain updates.
Behavior-scoped diagrams are needed when documenting durable domain knowledge across bounded contexts. They feature reusable fragments with canonical ownership and anchor-based cross-references, enabling composite rollups for complex scenario navigation.
This approach suits long-lived services and multi-area monorepos by keeping business rules, architectural decisions, and implementation slices synchronized. It applies structural invariants verified via bash smoke tests to prevent documentation drift over time.
trueraCreate and curate ground-truth evaluation datasets for TruLens.
mrgeoffrichRebuild API documentation and audit permissions from source code.
atanakaGenerate CRUD HTML fragments from UML class diagram inputs.
scanadyCreate and index Architecture Decision Records using MADR and other templates.
