ywc-wayfinder
(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: "wayfinder", "길찾기", "discovery map", "multi-session discovery", "탐색 ticket", "経路整理", "探索マップ", "ywc-wayfinder". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker/database writes outside the local Markdown map.
- License 许可
- MIT
- 最近更新
- 2026-11-08
- Stars
- ★ 8
- Forks
- 1
01 前言 Front Matter
- name
- ywc-wayfinder
- description
- (ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: "wayfinder", "길찾기", "discovery map", "multi-session discovery", "탐색 ticket", "経路整理", "探索マップ", "ywc-wayfinder". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker/database writes outside the local Markdown map.
02 资源文件 9
- 参考文档agents/openai.yaml300 B
- 参考文档evals/evals.json1.2 KB
- 参考文档README.en.md667 B
- 参考文档README.es.md751 B
- 参考文档README.ja.md751 B
- 参考文档README.ko.md811 B
- 参考文档README.md1010 B
- 参考文档README.zh.md698 B
- 参考文档references/map-ticket-contract.md2.0 KB
03 SKILL.md 正文
ywc-wayfinder
Announce at start: "I'm using the ywc-wayfinder skill to manage a deterministic local discovery map with one active ticket."
This skill manages a local Markdown map for large or uncertain discovery work. It does not implement code, does not write to external trackers, and resolves at most one active ticket per session before routing the next step.
Rationalization Defense
| Excuse | Reality |
|---|---|
| "This looks fuzzy, I'll just start coding and document later" | Wayfinder exists for fuzzy, multi-session discovery. If uncertainty is still material, coding first hides the unresolved decisions instead of shrinking them. |
| "I'll keep two active tickets open so I can explore faster" | Exactly one active ticket is the contract. Multiple active tickets destroy resume safety and make terminal status ambiguous. |
| "The map is only a note, I can rewrite history when resuming" | The map is the local source of truth. Resume must preserve ticket state, evidence, and next context exactly enough for the next session to continue deterministically. |
| "If everything is resolved, I'll still append a summary ticket" | Terminal maps do not write. When all tickets are resolved, return DONE without mutating the map. |
| "Deferred or blocked tickets can still be marked done if the route is obvious" | Deferred or blocked terminal state is NEEDS_CONTEXT, not DONE. A route idea is not the same as resolved context. |
| "This can replace normal planning now that the map exists" | Wayfinder is for discovery, not ordinary planning. Once the route is clear, hand off to ywc-plan, ywc-tech-research, or another downstream skill. |
Workflow
-
Qualify the request
- Use this skill only when the request is large, uncertain, or likely to span multiple sessions.
- If the request is ordinary planning or a single-session design discussion, route to
ywc-planorywc-brainstorminstead.
-
Resolve the map path
- The canonical artifact is
docs/ywc-plans/<slug>-wayfinder.md. - If the map does not exist, create it with the canonical fields from references/map-ticket-contract.md.
- If the map exists, validate its structure before using it.
- The canonical artifact is
-
Enforce one active ticket
- The map may contain many tickets, but only one may be marked active.
- If zero active tickets remain and unresolved work still exists, return
NEEDS_CONTEXT. - If more than one active ticket exists, return
NEEDS_CONTEXTwithout writing.
-
Work one ticket
- Update only the active ticket's evidence, route, and next-context fields.
- Route unresolved implementation work onward; do not implement it here.
- If the active ticket is invalid, stale, or contradicts the map state, return
NEEDS_CONTEXTwithout writing.
-
Handle terminal states
- If all tickets are resolved, return
DONEand do not write the map again. - If the best terminal state is deferred or blocked, return
NEEDS_CONTEXTand do not write.
- If all tickets are resolved, return
-
Route onward
- Use
ywc-planfor a clarified implementation plan. - Use
ywc-tech-researchwhen the ticket is blocked on external technical comparison. - Use
ywc-task-generatoronly after a downstream planning/spec path produces a finalized spec. - When a persisted
ywc-tech-research --outputartifact informs the route, record its project-relative Markdown path in the map so later skills can reuse the same provenance and overwrite contract.
- Use
Output Format
Map: docs/ywc-plans/<slug>-wayfinder.md
Ticket: <ticket-id>
Route: <next skill or stop reason>
Completion Status: DONE | NEEDS_CONTEXT
Validation
bash codex/skills/ywc-skill-author/scripts/validate-skill.sh codex/skills/ywc-wayfinderbash scripts/run-codex-skill-contract-evals.shbash scripts/validate.sh
Integration
- Upstream: Large ambiguous requests, resumed discovery sessions, or downstream skills that need a local discovery handoff.
- Downstream:
ywc-plan,ywc-tech-research,ywc-spec-ready, or another planning/research skill once the route is clear. - Never downstream directly to implementation: Executors and code-generation skills require a clearer contract than a discovery ticket provides.
04 同仓库更多 Skills
missing-frontmatter
暂无简介
malformed-frontmatter
暂无简介
fixture-501-fail
(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.
fixture-500-pass
(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.
ywc-worktrees
(ywc) Use when creating, auditing, pruning, or resolving git worktrees for isolated task workspaces, whether delegated from an executor or used standalone. Triggers: "worktree 생성", "worktree audit", "worktree 정리", "worktree prune", "ywc-worktrees", "create worktree". Do not use for branch creation/deletion alone, PR creation (use ywc-create-pr), CI or merge delivery (use ywc-finish-branch), task orchestration (use ywc-sequential-executor or ywc-parallel-executor), or non-git isolation.
ywc-wayfinder
(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: "wayfinder", "길찾기", "discovery map", "multi-session discovery", "탐색 ticket", "経路整理", "探索マップ", "ywc-wayfinder". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker/database writes outside the local Markdown map.