Update to Matt Skills Curated

{
  "description": "Map and navigate large, uncertain multi-session efforts through a shared graph of decision tickets. Use when facing complex greenfield projects or massive architectural migrations that exceed a single session — even if the user says \"map out this massive project\". Do NOT use for small, well-scoped features.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 101
    }
  ],
  "name": "wayfinder",
  "skill_md_contents": "---\nname: wayfinder\ndescription: \"Map and navigate large, uncertain multi-session efforts through a shared graph of decision tickets. Use when facing complex greenfield projects or massive architectural migrations that exceed a single session — even if the user says \\\"map out this massive project\\\". Do NOT use for small, well-scoped features.\"\n---\n\n# Wayfinder\n\nChart, navigate, and incrementally resolve large, uncertain multi-session architectural efforts through an evolving graph of decision tickets and clear frontier discovery.\n\n---\n\n## Core Invariants\n\n1. **Plan Over Do**: Wayfinder tickets resolve decisions, investigate unknowns, or validate prototypes—not raw execution slices.\n2. **Single Canonical Map Issue**: Maintain a single root tracker issue labeled `wayfinder:map` as the low-resolution index linking all child decision tickets.\n3. **One Decision Ticket Per Session**: A single agent session claims and resolves at most ONE decision ticket (excepting parallel research subagents).\n4. **Frontier Claim Protocol**: A session must explicitly assign the decision ticket to itself before beginning work to prevent multi-agent collision.\n5. **Fog-of-War Graduation**: Never pre-slice blurry, distant work into speculative tickets; keep them in `## Not yet specified` until the frontier reaches them.\n\n---\n\n## Architecture & Map of Content (MOC)\n\n```\n[ Massive Uncertain Initiative ]\n                │\n                ▼\n┌───────────────────────────────────────┐\n│ 1. Chart Destination & Map Issue      │ ──► Issue `wayfinder:map`\n│    (Notes, Fog sketches, Boundaries)  │\n└──────────────────┬────────────────────┘\n                   │\n                   ▼\n┌───────────────────────────────────────┐\n│ 2. Frontier Decision Tickets          │ ──► Child issues (`research`, `prototype`, `grilling`, `task`)\n│    (Unblocked, unclaimed questions)   │\n└──────────────────┬────────────────────┘\n                   │\n                   ▼\n┌───────────────────────────────────────┐\n│ 3. Atomic Session Resolution          │ ──► Post resolution comment, close issue,\n│    (Claim 1 ticket, settle decision)  │     update `Decisions so far`, graduate fog\n└───────────────────────────────────────┘\n```\n\n| Ticket Type | Execution Mode | Purpose |\n|---|---|---|\n| **Research** | AFK Subagent | Documentation, API discovery, external facts |\n| **Prototype** | HITL Interactive | Throwaway exploratory code (`skills/prototype/SKILL.md`) |\n| **Grilling** | HITL Interactive | Socratic decision distillation (`skills/grilling/SKILL.md`) |\n| **Task** | AFK or HITL | Manual prerequisite unblocking (e.g. account setup, credential provisioning) |\n\n---\n\n## Step-by-Step Procedure (TWI)\n\n### Step 1: Chart the Destination & Map Root\n- **Action**: Grill the user breadth-first to define the destination (the ultimate spec, architecture, or migration target) and establish the `wayfinder:map` root issue.\n- **Key Point**: If the route is already completely clear without fog, stop and route directly to `to-spec`.\n- **Why**: Wayfinding overhead is warranted only when substantial unknown decisions lie between the starting point and destination.\n\n### Step 2: Formulate Frontier Child Tickets & Wire Dependencies\n- **Action**: Create sharp child issues for immediate unblocked decisions and wire native blocking relationships.\n- **Key Point**: Keep un-sharp future ideas in the `## Not yet specified` section of the map.\n- **Inline Checklist**:\n  - [ ] Map created with clear Destination and Notes\n  - [ ] Immediate decision questions ticketed and labeled\n  - [ ] Blocking dependencies wired in tracker\n  - [ ] Research tickets dispatched to background subagents\n\n### Step 3: Claim and Resolve a Single Frontier Ticket\n- **Action**: Assign the chosen frontier ticket to self, execute the investigation/grilling, and produce the decision verdict.\n- **Key Point**: Post the decision as a resolution comment on the issue and close it.\n- **Why**: Immediate closure and commentary keep the frontier clean and transparent for concurrent team members.\n\n### Step 4: Update Map Index & Graduate Fog\n- **Action**: Add a one-line summary to `## Decisions so far` on the map issue and graduate freshly specifiable items from `## Not yet specified` into new tickets.\n- **Key Point**: If a path is determined to be outside the destination scope, move it to `## Out of scope` and close any associated tickets.\n- **Why**: Incremental fog clearing keeps the map accurate without speculative bloat.\n\n---\n\n## Anti-Rationalization Guardrails\n\n| Tempting Rationalization | Binding Rule | Engineering Rationale |\n|---|---|---|\n| *\"I'll resolve 4 tickets in this single session.\"* | **Enforce 1 decision ticket per session.** | Multi-ticket batching causes context exhaustion and sloppy decision records. |\n| *\"Pre-create 20 tickets for all future phases.\"* | **Keep blurry work in 'Not yet specified'.** | Pre-slicing the fog creates brittle tickets that get invalidated by early decisions. |\n| *\"Start building the final feature code during wayfinding.\"* | **Wayfinder produces decisions, not deliverables.** | Premature implementation while architecture is foggy leads to massive rewrites. |\n\n"
}