Catalog
Yeachan-Heo/map

The yard's skill map — which skill owns which job, in delivery-loop order. Use when something needs doing but not which of the shipped skills owns it; the map routes, it never executes.

NewUpdated Nov 8, 2026

Map

You know something needs doing; you do not know which skill owns it. Find the job below and follow its route. Most routes call the Skill tool; a route marked manual gives you the slash command to invoke yourself because model invocation is disabled. The map routes and explains nothing twice — each routed skill owns its own doctrine.

The delivery loop

You are here Skill
External work arrived (issues, PRs, reports) harbor
A non-engineer handed you a chat log as requirements intent
The destination is foggy — the first three decisions cannot be stated yet ask-navigator
Vague idea; questions must come before anything else deep-interview
Requirements are clear; you need a plan plan (multi-perspective consensus: ralplan)
Approved plan; decompose and ship end to end with human checkpoints launch
One task; persistence until verified complete ralph
Hands-off idea-to-code autopilot
Work needs coordinated parallel workers team
One approved task carried through verified code execute
One attempt risks locking in the wrong shape arena
Code crosses a function boundary; designs should compete first architect
Finished work needs attack before it ships interrogate
A design question prose cannot settle loft
Finished work needs judgment review
Something claims to be done verify
Work is landing as a PR pr
An open PR needs driving to merge-ready babysit
The run taught the environment something refit

On-ramps (off the main loop)

Job Skill
A bug needs its root cause debug; competing-hypothesis tracing: trace
The question is why the code is this way why
A subsystem needs explaining how; as a lesson: teach
A risky change needs its blast radius mapped blast-radius
The same agent mistake keeps recurring correct
Long autonomous work needs an audit trail show-me-your-work
No bundled skill fits the task shape figure-it-out (designs one, validated against anchors)
A property tests cannot reach needs formal proof create-formal-verification-skill; drifted spec: maintain-formal-verification-skill
A flow or protocol bug shows up as a path through states statechart
The repo needs its own verification commands recorded create-verification-skill; drifted commands: maintain-verification-skill
Roles should run on chosen models models
Tests should drive the implementation tdd
The codebase is getting harder to change architecture-survey
AI-generated slop needs cleanup ai-slop-cleaner
A measured number needs vetting before it is reported or acted on benchmark-checklist
A delegated brief needs cross-cutting judgment guardrails principles
An open question needs grounded answers research; external docs: external-context
Knowledge should compound across sessions wiki; durable project memory: remember
A recurring autonomous improvement loop self-improve; durable goal ledger: ultragoal
A session needs reorientation across its pivots and outcomes session-flow — run /oh-my-claudecode:session-flow manually
Visual work needs verdicts or diagrams visual-verdict; diagram

Utilities

Job Skill
Install, diagnose, configure omc-setup; omc-doctor; configure-notifications
Manage skills themselves skill (local); skillify (extract from session)
Inspect orchestration state trace (also the tracing lane); graph (DAG runtime)
Cancel a mode cancel
CI is red on a PR you own fix-ci; review threads: get-pr-comments; conflicts: fix-merge-conflicts
The user missed the session ketchup; as a subtitled video: ketchup-video; after a break or crash: recall
A brief is vague sharpen; playback before starting: in-your-own-words
A reply was too dense bro
Shipping prose needs the standard technical-writing; TS type discipline: typescript-best-practices
The period's authored work needs summarizing what-did-i-get-done
A queue must land as one stacked PR chain stacked-delivery; watch state: babysit
A measured target needs climbing over multiple rounds hillclimb
A long session's lessons should be banked as skill edits reflect; extraction: skillify
A cross-project personal behavior profile is wanted personal-mode; single facts: remember

Rules

  • The map routes; it never executes. Each ordinary row resolves to one Skill-tool call — make it, then follow that skill's doctrine. For a manual-only route, show the user its slash command; do not try to call the Skill tool.
  • When two rows both fit, the delivery loop above is the tiebreak: earlier legs come first.
  • Phase boundaries (continue / re-enter from disk / hand off / compact) are defined in launch's Context hygiene — the map does not restate them.
  • A job matching no row is itself information: say so plainly rather than picking the nearest-sounding skill.
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

88/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

98

Quality

85

Clarity

90

Completeness

79

Summary

The **map** skill is a meta-routing guide that directs agents to the correct specialized skill based on the type of work needed. It contains no executable code, makes no tool calls itself, and operates as a read-only decision tree with 50+ job-to-skill mappings organized across three sections: delivery loop (main workflow), on-ramps (specialized branches), and utilities. The skill's purpose is informational — it documents the complete skill ecosystem and helps agents find the right tool without executing any operations.

Detected Capabilities

read-only navigationdecision routingskill selection guidance

Trigger Keywords

Phrases that agents use to match this skill to user intent.

which skill owns thisroute to correct skillfind the right skillskill ecosystem mapdelivery loop routingtask routing decision

Use Cases

  • Route a task to the correct skill when starting work with unclear ownership
  • Understand the delivery loop and skill dependencies in the yard ecosystem
  • Find specialized skills for debugging, verification, and on-ramp scenarios
  • Determine which utility skill handles setup, CI issues, or session management
  • Resolve skill routing ambiguity by consulting tiebreaker rules based on workflow order

Quality Notes

  • Comprehensive skill ecosystem mapping — 50+ job-to-skill routes organized logically across three sections
  • Clear hierarchical structure with delivery-loop ordering and explicit tiebreaker rules for routing ambiguity
  • Each route description is concise and uses consistent terminology (paired skills like plan/ralplan, trace/debug shown inline)
  • Frontmatter correctly sets disable-model-invocation:true, preventing accidental execution
  • Documentation clearly states the skill's scope: 'routes and explains nothing twice' — each routed skill owns its own doctrine
  • On-ramps section effectively maps domain-specific problems (formal verification, statecharts, benchmarking) to dedicated skills
  • Utilities section groups operational and meta-skills (setup, skill management, CI fixes, session recovery) for easy discovery
  • Well-suited for skill discovery and disambiguation — agent can immediately identify which skill to call next
Model: claude-haiku-4-5-20251001Analyzed: Nov 8, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v1.2

    Content updated

    ✦ AIExpands delivery loop, on-ramps, and utilities with 13 new skill roles for design competition, risk mapping, formal verification, statecharts, measurement vetting, and session continuity.

    2026-11-08

    LATEST
  2. v1.1

    Content updated

    ✦ AIIntroduces manual-only routes that require direct slash commands instead of Skill-tool calls.

    2026-10-13

    View This Version
  3. v1.0

    2026-10-02

    View This VersionInitial version

Use Yeachan-Heo/map in your dev environment

Command Palette

Search for a command to run...