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…
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…
Use when starting the HAMLET live-visualization stack — the townlet inference server plus the Vue frontend — to watch trained agents run from checkpoints in a browser.
Use when building Vue 3 components, creating dashboards, implementing forms, optimizing data-heavy interfaces, or making designs responsive. Mandates design tokens, accessibility, proper state management, error states, and template cleanliness for…
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…
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…
Use when assessing codebase architecture and you feel pressure to soften critique, lead with strengths, or frame problems diplomatically - provides evidence-based critical assessment resisting relationship and economic pressures
Use when cataloging technical debt under time pressure and tempted to explain choices instead of delivering document - enforces execution discipline with scoped delivery patterns for partial catalogs