| name | doc-driven-workflows |
| description | Use only when the user explicitly invokes $doc-driven-workflows, or an active workflow/project instruction routes here, for doc-driven code/docs sync, architecture/tech-stack/operation-flow/call-path docs, alignment review, open-question ledgers, or required source-of-truth maintenance. Do not use merely because docs exist. |
Doc-Driven Workflows
Maintain durable, source-backed project truth. This skill owns architecture,
tech stack, operation flows, call paths, project operating model, and
doc-driven open-question ledgers.
Iron Law
NO DOC SYNC WITHOUT AN INVOCATION GATE AND SOURCE EVIDENCE.
Docs that merely exist, docs that are absent, or theoretical drift do not
trigger this workflow.
Use For
- explicit doc-driven work
- code/docs alignment review
- source-backed architecture, tech-stack, operation-flow, or call-path docs
- open-question ledgers for durable uncertainty
- maintenance when current work would make declared source-of-truth docs stale
Do not use for ordinary docs edits, discussion recap, lane integration, or code
implementation.
Gates
- Entry valid: explicit
$doc-driven-workflows, an active workflow route, or a
project instruction that explicitly requires this maintenance.
- Mode resolved from
references/modes-and-gates.md: bootstrap, maintenance,
or no-op.
- Maintenance eligible: declared source-of-truth docs may actually drift;
evidence is current from source, config, tests, runtime, or guidance.
- Fact has one home. Link instead of duplicating.
- Uncertainty goes to the open-question ledger, not confirmed docs.
Refinement
Raw inbox material, vendor docs, SDK notes, screenshots, agent outputs, and
research excerpts are not project truth. Promote only refined, project-specific
contracts, flows, call paths, constraints, risks, evidence, or open questions.
Core question:
Would future readers misunderstand how to operate, integrate, run, modify, or
trust the system if docs stayed unchanged?
If no, stay quiet.
References
Read only what the mode needs:
- Always read modes-and-gates.md after this
skill is invoked to resolve bootstrap, maintenance, or no-op.
- Read document-patterns.md only when creating
or materially changing a doc-driven documentation set.
- Read project-shapes.md for bootstrap, or when
maintenance changes project shape, workspace layout, or an
architecture-shaping dependency.
Language
Reply in the user's current language. Preserve existing document language during
maintenance unless the user asks otherwise.
Output
Lead with changed documentation and source evidence. Preserve material open
questions and intentional skips; omit repeated background:
Docs updated:
Evidence:
Open questions:
Skipped:
Omit empty headings. Do not include broad next steps unless asked.
Red Flags
- Bootstrapping because docs are missing.
- Running maintenance for every coding task.
- Writing speculation into confirmed docs.
- Copying raw external docs into durable truth.
- Creating duplicate fact homes.
- Claiming alignment without checking current source anchors.
