thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this…
Zero-friction idea capture. Append, list, or promote notes to todos.
$ npx -y skills add SienkLogic/plan-build-run --skill note --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/noteContext preview
The summary Claude sees to decide when to auto-load this skill.
Zero-friction idea capture. Append, list, or promote notes to todos.
name: note description: "Zero-friction idea capture. Append, list, or promote notes to todos." allowed-tools: Read, Write, Glob, Grep argument-hint: "<text> | list | promote <index> [--global]"
**STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~7,600 tokens. Begin executing Step 1 immediately.**
**Before ANY tool calls**, display this banner:
╔══════════════════════════════════════════════════════════════╗ ║ PLAN-BUILD-RUN ► NOTE ║ ╚══════════════════════════════════════════════════════════════╝
Then proceed to Step 1.
You are running the **note** skill. Your job is zero-friction idea capture. One Write call, one confirmation line. No questions, no prompts.
This skill runs **inline** — no Task, no AskUserQuestion, no Bash.
---
Notes are stored as **individual markdown files** in a notes directory:
Each note file has this format:
---
date: "YYYY-MM-DD HH:mm"
promoted: false
---
{note text verbatim}**`--global` flag**: Strip `--global` from anywhere in `$ARGUMENTS` before parsing. When present, force global scope regardless of whether `.planning/` exists.
**Important**: Do NOT create `.planning/` if it doesn't exist. If there's no `.planning/` directory, fall back to global scope silently.
---
Parse `$ARGUMENTS` after stripping `--global`:
| Condition | Subcommand | |-----------|------------| | Arguments are exactly `list` (case-insensitive) | **list** | | Arguments are exactly `promote <N>` where N is a number | **promote** | | Arguments are empty (no text at all) | **list** | | Anything else | **append** (the text IS the note) |
**Critical**: `list` is only a subcommand when it's the ENTIRE argument. `/pbr:note list of groceries` saves a note with text "list of groceries". Same for `promote` — only a subcommand when followed by exactly one number.
---
Create a timestamped note file in the target directory.
1. Determine scope (project or global) per Storage Format above 2. Ensure the notes directory exists (`.planning/notes/` or `~/.claude/notes/`) 3. Generate slug via CLI:
pbr-tools slug-generate "{note text}"Parse the JSON output to get the `slug` field. 4. Generate filename: `{YYYY-MM-DD}-{slug}.md`
5. Write the file with frontmatter and note text (see Storage Format) 6. Confirm with exactly one line: `Noted ({scope}): {note text}`
---
Show notes from both project and global scopes.
1. Glob `.planning/notes/*.md` (if directory exists) — these are "project" notes 2. Glob `~/.claude/notes/*.md` (if directory exists) — these are "global" notes 3. For each file, read frontmatter to get `date` and `promoted` status 4. Exclude files where `promoted: true` from active counts (but still show them, dimmed) 5. Sort by date, number all active entries sequentially starting at 1 6. If total active entries > 20, show only the last 10 with a note about how many were omitted
Notes:
Project (.planning/notes/):
1. [2026-02-08 14:32] refactor the hook system to support async validators
2. [promoted] [2026-02-08 14:40] add rate limiting to the API endpoints
3. [2026-02-08 15:10] consider adding a --dry-run flag to build
Global (~/.claude/notes/):
4. [2026-02-08 10:00] cross-project idea about shared config
{count} active note(s). Use `/pbr:note promote <N>` to convert to a todo.If a scope has no directory or no entries, show: `(no notes)`
---
Convert a note into a todo file.
1. Run the **list** logic to build the numbered index (both scopes) 2. Find entry N from the numbered list 3. If N is invalid or refers to an already-promoted note, tell the user and stop 4. **Requires `.planning/` directory** — if it doesn't exist, warn: "Todos require a Plan-Build-Run project. Run `/pbr:new-project` to initialize one, or use `/pbr:add-todo` in an existing project." 5. Ensure `.planning/todos/pending/` directory exists 6. Generate todo ID: `{NNN}-{slug}` where NNN is the next sequential number (scan both `.planning/todos/pending/` and `.planning/todos/done/` for the highest existing number, increment by 1, zero-pad to 3 digits) and slug is generated via CLI:
pbr-tools slug-generate "{note text}"Parse the JSON output to get the `slug` field. 7. Extract the note text from the source file (body after frontmatter) 8. Create `.planning/todos/pending/{id}.md`:
---
title: "{note text}"
status: pending
priority: P2
source: "promoted from /pbr:note"
created: {YYYY-MM-DD}
theme: general
---
## Goal
{note text}
## Context
Promoted from quick note captured on {original date}.
## Acceptance Criteria
- [ ] {primary criterion derived from note text}9. Mark the source note file as promoted: update its frontmatter to `promoted: true` 10. Confirm: `Promoted note {N} to todo {id}: {note text}`
---
1. **"list" as note text**: `/pbr:note list of things` → saves note "list of things" (subcommand only when
Plan it. Build it. Run it. A Claude Code plugin for structured development with context-engineered agents.
Repo: SienkLogic/plan-build-run
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this…
Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.
Review past Claude Code sessions for PBR workflow compliance and UX quality.
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
Manage backlog items — ideas not ready for active planning. Add, review, promote, or remove.
Start a new project. Deep questioning, research, requirements, and roadmap.