Skip to content

borghei/Claude-Skills / project-management/execution/wayfinder

wayfinder

Verified

Chart work too big for one sprint as a map of decision tickets, resolve them in dependency order, then turn answers into tracer-bullet tickets. Use when the route is unclear, open questions block each other, or estimates swing wildly.

assets/decision_map_template.md

View on GitHub
# Map: <effort name>

> One map per effort. The map is an index, not a store: each decision lives on its
> own ticket, and this page only points at it. Load this page at the start of every
> working session, then pick one frontier ticket.

## Destination

<!-- One or two sentences. Observable end state, not an activity.
     Good: "New self-serve workspaces are billed per seat-hour and every invoice
     reconciles to the ledger within 0.5% before close."
     Bad:  "Work on usage-based billing." -->

## Notes

<!-- Standing context every session needs: who owns which calls, constraints that
     are not up for debate, vocabulary, working cadence ("one decision per session"),
     where tickets live and which label marks them. -->

- Decision owners:
- Fixed constraints:
- Tracker / label:
- Cadence:

## Decisions so far

<!-- One line per resolved decision ticket, in the order resolved:
     - [<ticket title>](link) — <gist of the answer in one clause>
     Never restate the reasoning here; it lives on the ticket. -->

## Not yet specified (fog)

<!-- In-scope questions you can sense but cannot yet phrase sharply. Note what each
     one hangs on. When a resolution makes one sharp, delete it here and open a
     ticket — it must live in exactly one place. -->

- <suspected question> — hangs on <ticket or fact>

## Out of scope

<!-- Work consciously ruled beyond the destination, each with a one-line reason.
     These never graduate; they return only if the destination is redrawn. -->

- <item> — <why it sits past the destination>

## Implementation tickets

<!-- Filled in as decisions resolve. Each line is a tracer-bullet slice or a phase
     of an expand-migrate-contract refactor, with its blockers. -->

| Ticket | Derived from | Blocked by | Status |
|--------|--------------|------------|--------|
|        |              |            |        |

## Map health (update each session)

- Frontier tickets:
- Decisions open / resolved:
- Oldest open decision and its decide-by date:
- Validator result (`decision_map_validator.py`): PASS / FAIL
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall