mirror of
https://github.com/mattpocock/skills.git
synced 2026-07-29 02:52:42 +07:00
People kept reading a wayfinder ticket as an ordinary implementation ticket — a slice of a build to execute — when wayfinder uses them as decision tickets: questions whose resolution is a decision. Introduce "decision ticket" as a light leading word: the skill description and its opening line name it (and say what makes it one), and the ask-matt / engineering README blurbs and the docs page match, while "ticket" stays the everyday word once the term is established. Record "Decision ticket" in CONTEXT.md so the "avoid: ticket" domain rule no longer contradicts wayfinder's deliberate use of the word. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
705 B
705 B
mattpocock-skills
| mattpocock-skills |
|---|
| patch |
Name the /wayfinder unit a decision ticket.
People kept reading a wayfinder ticket as an ordinary implementation ticket — a slice of a build to execute — when wayfinder uses them as decision tickets: questions whose resolution is a decision. The skill description and its opening line now introduce "decision ticket" (and say what makes it one), and the ask-matt / engineering README wayfinder blurbs and the docs page match — while "ticket" stays the everyday word once the term is established. CONTEXT.md records Decision ticket as a domain term so the "avoid: ticket" guidance no longer contradicts wayfinder's deliberate use of the word.