Code-grounded intent for the Weft suite — a code-UP traceability graph (SEI → requirement → goal). Advisory, local-first; consumes the Loomweave SEI, never mints, renders no release verdict.
This skill should be used when the user asks to "track work", "create an issue", "find something to work on", "what should I work on next", "triage bugs", "close an issue", "check what's blocked", "plan a milestone", "review sprint progress", "coordinate agents", or when working in a project that uses filigree for…
This skill should be used when the user asks to explain or evaluate a policy cell, submit a graded override, check the override-rate CI gate, run a governance gate, read git branch/commit context, read the git-rename feed for Loomweave, gate a Filigree closure on verified binding evidence, route Wardline scan findings…
Use when orienting in an unfamiliar or large codebase and you want to avoid re-reading or grepping the whole source tree: answering "what calls X", "where is X defined", "what does X depend on", "what subsystem is X in", or "find the function/class/module that does Y". Applies whenever a Loomweave code-archaeology MCP…
This skill should be used when the user asks "why does this code exist", "what's our intent coverage", "find orphan code / requirements / goals", "trace this requirement up to a goal or down to code", "bind this SEI / entity to a requirement", "draft / approve / supersede a requirement", "show the requirement…
Use when scanning for or fixing trust-boundary / taint findings, when a wardline scan reports a defect, or when wiring wardline into an agent's edit-verify loop. Explains the scan -> explain -> fix-at-the-boundary -> rescan cycle and the baseline-vs-waiver discipline.
Use when the user asks "what changed", "what breaks if I touch X", "what is the blast radius / change impact", "what should I re-verify before claiming done", "show the timeline / churn for this entity", or when working in a project that uses warpline for temporal change-impact tracking. warpline is the Weft…