concept-guardrails
Installation
SKILL.md
Concept Guardrails
Focus: do existing specifications state module contracts clearly and correspond to facts and derived
maps? Run only on explicit $concept-guardrails invocation. The workflow adapts
wyx v0.26.0 under MIT (LICENSE.upstream); specifications use
this repository's Jackson dialect while runtime scripts retain upstream behavior.
Authority Model
CONCEPT.mddefines purpose, state, actions, and operational principle; optional notes hold application context.SYNCS.mdrecords app/include/sync coordination for application purposes and scenarios; when/where/then define rules and// flow:groups them.PIPELINE.mdrecords sources, stages, outputs, invariants, triggers, and data boundaries without replacing synchronizations.ARCHITECTURE.mdis a derived navigation map. Product dependencies come from the overall PRD, not synchronization edges.- Backfill reconstructs evidenced contracts from implementation; drift compares implementation with contract. Neither proves fitness for purpose.