A loose idea has arrived — too big for one agent session, and wrapped in fog: the route from here to a plan isn't visible yet. This skill charts it: stand up a map, then work its tickets one at a time until the way to the goal is clear. The map is domain-agnostic — engineering work, course content, whatever fits the shape. The Map The map is a single compact Markdown file, one per wayfinding effort, git-tracked alongside the project. It is the canonical artifact — the whole map is loaded as context into every session , so it must stay compact. Assets created during tickets should be linked to from the map, not duplicated within it. Structure Entries ("tickets"), each its own section keyed by a short dash-case slug that reads as a mini-title (e.g. relational-db , auth-strategy , cache-layer ) — terse enough to stay token-efficient, and unique within the map.
relational-db: Relational Or Non-Relational Database? Show more Installs 790 Repository mattpocock/skills GitHub Stars 152.1K First Seen 1 day ago Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass