Skip to content
Back to search

waypoint

MarketplaceWorks with Claude CodeGitHub

Waypoint: a goals pane for Claude Code, with focus, sub-tasks and standups

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/AhmedHisham552/waypoint with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/AhmedHisham552/waypoint'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ahmedhisham552--waypoint/badge.svg)](/listings/ahmedhisham552--waypoint)

HTML

<a href="/listings/ahmedhisham552--waypoint"><img src="/api/listings/ahmedhisham552--waypoint/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

/plugin install waypoint --marketplace AhmedHisham552/waypoint

Answer `y` to add the marketplace, then pick **user** scope so the pane is there in every project. Then:

/track add @here Ship onboarding guide; Fix flaky login test
/track sub 1 Outline; First draft; Screenshots; Review
/track focus 1

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 13 lines
  1. {
  2. "name": "waypoint",
  3. "owner": {
  4. "name": "Ahmed Hisham"
  5. },
  6. "plugins": [
  7. {
  8. "name": "waypoint",
  9. "source": "./"
  10. }
  11. ],
  12. "description": "Waypoint: a goals pane for Claude Code, with focus, sub-tasks and standups"
  13. }
README.md · README · 180 lines
  1. # Waypoint
  2. **A goals pane for Claude Code, driven by `/track`.** Keep the few things you want to get done beside the chat, see what you are working on *now*, tick sub-tasks as you go, and get your standup or weekly review written for you from what actually happened.
  3. [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
  4. [![Claude Code plugin](https://img.shields.io/badge/Claude%20Code-plugin-d97757)](https://docs.claude.com/en/docs/claude-code/plugins)
  5. ```
  6. ◎ Waypoint · Goals 0/4
  7. ──────────────────────────────
  8. Now 2/4
  9. ◑ #3 Ship onboarding guide
  10. ✓ 3.1 Outline
  11. ✓ 3.2 First draft
  12. ○ 3.3 Screenshots
  13. ○ 3.4 Review
  14. my-app
  15. ○ #6 Fix flaky login test 0%
  16. General
  17. ◕ #2 Prepare demo 3/4
  18. ▸ other-repo 2
  19. ```
  20. ## Quick start
  21. ```
  22. /plugin install waypoint --marketplace AhmedHisham552/waypoint
  23. ```
  24. Answer `y` to add the marketplace, then pick **user** scope so the pane is there in every project. Then:
  25. ```
  26. /track add @here Ship onboarding guide; Fix flaky login test
  27. /track sub 1 Outline; First draft; Screenshots; Review
  28. /track focus 1
  29. ```
  30. ## Features
  31. - **Side pane** that stays beside the chat, about 32 columns wide.
  32. - **Focus.** One goal is *NOW*: it sits on top with its sub-tasks, and the hint line under the prompt keeps it in view, faded.
  33. - **Hands-off updates.** Claude sees your open goals with each prompt. When you start talking about another goal, it switches focus. When its work finishes a sub-task, it ticks it. A toast tells you, with a one-line undo.
  34. - **Live progress.** Whatever is being worked on spins in the pane (`⠹ 3.2 Screenshots`) until it's ticked. Claude and its agents mark sub-tasks as they start them.
  35. - **Sub-tasks** with a goal's progress worked out from them. Progress shows as a filling circle `○ ◔ ◑ ◕ ✓`.
  36. - **Labels per repo.** Goals added with `@here` belong to the repo you are in, and every worktree of that repo shares them. Other repos' labels show as one header line you can click to open. Untagged goals are **General**.
  37. - **Change log.** Adds, ticks, progress, focus and removals are recorded with their time and an optional note.
  38. - **Summaries.** `yesterday`, `today`, `week` or any date range, as an exact log plus a short update ready to paste into Slack or a standup thread.
  39. - **Work on goals from one session.** `/waypoint:work 1 3` has Claude gather context and ask you everything up front. Once you confirm, it dispatches one background agent per goal, with progress ticking into the pane as they finish.
  40. - **Ask about your log.** Claude answers "what did I do this week?" from your log.
  41. ## Usage
  42. | Command | What it does |
  43. | --- | --- |
  44. | `/track add A; B` | Add goals to General (`add` is optional) |
  45. | `/track add @here A` | Add a goal to the repo you are in |
  46. | `/track add @label A` | Add a goal to any label |
  47. | `/track sub 3 A; B` | Add sub-tasks to goal #3 |
  48. | `/track tick 3.2 "note"` | Tick (or untick) sub-task 3.2, with an optional note |
  49. | `/track 3 60 "note"` | Set progress of a goal without sub-tasks |
  50. | `/track done 3` | Mark goal #3 done |
  51. | `/track rm 3` / `rm 3.2` / `rm 5, 6, 3.2` | Remove goals and sub-tasks, one or many |
  52. | `/track focus 3` / `focus off` | Set or clear the NOW goal for that goal's label |
  53. | `/track start 3.2` / `stop` | Mark work in progress: it spins in the pane until ticked or stopped |
  54. | `/track tag 3 @label` | Move a goal to a label (`@general` to clear) |
  55. | `/track @label` | Open or close another label in the pane (or click its header) |
  56. | `/track yesterday` / `today` / `week` | Summary for that period |
  57. | `/track from 2026-11-01 to 2026-11-15` | Summary for any date range |
  58. | `/waypoint:work 1 3` | Plan and dispatch work on goals #1 and #3 (see below) |
  59. | `/waypoint:work 2.4 2.5 workflow` | Work on chosen sub-tasks only, run as workflows |
  60. | `/track done-list` | List finished goals |
  61. | `/track` | Open the pane and show help |
  62. Goal numbers (`#3`) are permanent: they never shift when other goals are added or removed. Sub-tasks are `goal.sub` (`3.2`).
  63. In the pane, a goal row sets focus and a sub-task row ticks it, by click or keyboard.
  64. **Ask Claude** in plain words: "add a goal to review the PR for this repo", "tick the screenshots sub-task", "write my standup". Claude uses the plugin's `update_goals` tool, which takes the same commands.
  65. ## Working on goals
  66. `/waypoint:work <n|n.m> … [agents|workflow]` (a skill that ships with the plugin) turns this session into an orchestrator. Pass whole goals (`1 3`), chosen sub-tasks (`2.4 2.5`), or both:
  67. 1. **Align.** Claude reads what it can from the code, docs and tools, adds sub-tasks to any goal without them, then asks you every question it needs answered, in one message.
  68. 2. **Dispatch.** Once you confirm, it starts one background agent per goal, or one workflow per goal with `workflow` (or the `dispatch` setting), each with a self-contained brief. Each agent ticks its sub-tasks in the pane as it finishes them, and stops to report a question rather than guess.
  69. 3. **Report.** As agents finish, Claude gives you each result in a few lines and brings you any question raised, then re-dispatches with your answer.
  70. ## Standups and weekly reviews
  71. `/track yesterday` (the last *working* day):
  72. ```
  73. Tue 17 Nov
  74. PLANNED 4 goals open, focus: Ship onboarding guide
  75. DONE ◑ Ship onboarding guide 2/4
  76. ✓ First draft
  77. ✓ Fix flaky login test
  78. MOVED ◔→◑ Prepare demo 1/4 → 2/4
  79. STILL OPEN Migrate settings page
  80. POST
  81. Yesterday I finished the first draft of the onboarding guide and sent it
  82. for comments, and fixed the flaky login test. The demo is halfway there.
  83. Today I'll add screenshots to the guide.
  84. ```
  85. - **PLANNED:** goals open at the start of the period, and what was in focus.
  86. - **DONE:** goals finished in the period, and finished sub-tasks under their goal. Each counts once, by its last state. Notes are left off screen but go into the post.
  87. - **MOVED:** goals that made progress but are not finished.
  88. - **STILL OPEN:** goals that did not move.
  89. - **POST:** a short update written by a small Claude model from the log above, and only from it: a standup update for a day, a short review for `week` and date ranges.
  90. `week` and date ranges group everything by label.
  91. ## How it works
  92. - **Files.** Everything lives in one folder (default `~/.waypoint`; an install from before the rename keeps reading `~/.claude-goals`):
  93. - `goals.json`: the current goals.
  94. - `log/YYYY-MM.jsonl`: one line per change, one file per month.
  95. Plain files, so you can back them up, sync them or grep them. They survive reinstalling the plugin.
  96. - **Labels.** `@here` resolves to the folder name of the repo's main checkout (`git rev-parse --git-common-dir`), so worktrees share a label. Outside git it is the current folder's name.
  97. - **Focus.** One NOW goal per label. A session shows the focus of its repo's label, or General's when that label has none.
  98. - **Finished goals** stay in the pane, green, on the day they were finished, then leave it. They stay in the log, the summaries and `/track done-list`.
  99. - **Two sessions at once.** Each change re-reads the files before writing, so one session doesn't wipe another's goals. Every open pane picks up changes from other sessions within a few seconds. In the rare case two sessions write in the same instant, one log line can be lost.
  100. ## Configuration
  101. Run `/plugin`, open **waypoint**, and set:
  102. | Option | Default | What it does |
  103. | --- | --- | --- |
  104. | `dataDir` | `~/.waypoint` | Folder for `goals.json` and `log/` |
  105. | `workWeek` | `sun-thu` | Working days for `yesterday` and `week` (`sun-thu` or `mon-fri`) |
  106. | `autoUpdate` | on | Claude may switch focus and tick sub-tasks on its own from the conversation |
  107. | `dispatch` | `agents` | How `/waypoint:work` runs each goal: `agents` (lighter) or `workflow` (more thorough, uses more agents) |
  108. The pane docks beside the chat in the fullscreen layout on a terminal at least 110 columns wide. To have that in every session, with no flag to remember, add this to `~/.claude/settings.json`:
  109. ```json
  110. { "env": { "CLAUDE_CODE_NO_FLICKER": "1" } }
  111. ```
  112. Otherwise it shows above the prompt. Run `/track` once: from then on the pane docks by itself from 110 columns (144 before you have opened it). Drag its edge to resize it; your width is kept.
  113. ## Data and privacy
  114. Your goals and log are stored on your machine, in `dataDir`. Two things go to Claude, as part of your normal Claude Code usage:
  115. - **With `autoUpdate` on:** your open goals and sub-tasks are attached to each prompt you send, so Claude can keep them current. Turn `autoUpdate` off to stop this.
  116. - **When you ask for a summary:** the summary log is sent to a small Claude model to write the POST.
  117. ## Troubleshooting
  118. - **The pane is not beside the chat.** Use the fullscreen layout (above) and a terminal at least 110 columns wide, or open the pane with `/track`.
  119. - **The circles look misaligned.** Some fonts draw `◔ ◑ ◕` at a different width. Please open an issue with your terminal and font.
  120. - **My v0.1 goals are gone.** v0.2 imports them once, on its first start, into the `dataDir` set at that moment. If you changed `dataDir` later, move the files from the old folder into the new one.
  121. ## Development
  122. ```
  123. git clone https://github.com/AhmedHisham552/waypoint
  124. cd waypoint
  125. claude --plugin-dir . # run it from this folder
  126. claude plugin validate .
  127. claude plugin test .
  128. ```
  129. The code is a Claude Code hooks module in `hooks/`. `register.tsx` wires the events, and the logic is in plain modules: `model.ts`, `parse.ts`, `store.ts`, `label.ts`, `summary.ts` and `view.tsx`, each with a `*.test.ts` beside it.
  130. ## Contributing
  131. Issues and pull requests are welcome. Please run `claude plugin validate .` and `claude plugin test .` before opening a pull request, and update this README when you add or change a command.
  132. ## License
  133. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.