bugbook

Start-of-session orientation and review. Gets you up to speed on the project — reviews /go run results if there are any, shows what's in flight, what's blocked, and what happened since you last looked. Surfaces overnight discoveries from the knowledge loop. Writes a visual Session Brief page to Bugbook so you can review in the app. Use when the user says "catchup", "catch up", "what happened", "where are we", "what's the status", "bring me up to speed", "what did I miss", "morning review", "show me what you did", "what happened overnight", or starts a new session and wants to get oriented. Works with or without a prior /go run — it's the universal "start of session" skill.

Access your bugbook workspace — local-first notes, databases, and personal context. Use when the user wants to see their notes, tickets, databases, or personal knowledge.

Compile a Bugbook workspace into an agent-navigable wiki. Reads all pages, groups them by topic, generates a root Index.md that serves as the agent's entry point, and optionally creates summary articles for each category. Reusable — run once after a bulk import, then periodically as the workspace grows. Use when the user says "compile", "build my wiki", "generate index", "organize my notes", "compile my workspace", or after running /import-obsidian.

Smart parallel ticket dispatcher — analyzes file overlap across tickets, builds a dependency graph, groups tickets into conflict-free parallel lanes, and executes each lane in its own git worktree. The analysis and routing layer on top of /go. Use when the user says "dispatch tickets", "smart parallel", "parallelize these tickets", "run tickets without conflicts", "dispatch", "parallel dispatch", "multi-lane", or wants to execute multiple tickets simultaneously without merge conflicts.

Structured agent workflow that takes a Granola transcript or written description, creates tracked projects and tickets in Bugbook, executes them sequentially with status updates, and loops on human review until clean. Use this skill whenever the user wants to start a development workflow, process a meeting transcript into tasks, break work into tickets, or says "flow", "start a flow", "process this transcript", "break this into tickets", "here's what we discussed", or pastes meeting notes. Also use when the user pastes a Granola transcript, describes a batch of work to be done, or wants to turn a planning conversation into tracked action items.

Autonomous long-running execution — works through open tickets while the user is away. Claude orchestrates, writes evals, manages queue/status, and verifies every change. Codex CLI is the default implementation worker; Claude worktree agents are the fallback for complex multi-file work. Runs sequentially by default, with safe two-ticket parallelism only when tickets touch completely different files. Use when the user says "go", "let's go", "night", "goodnight", "do everything", "work on this while I sleep", "run overnight", "keep working", "don't stop", or signals they want autonomous unattended execution.

One-shot migration from an Obsidian vault into the canonical Bugbook workspace. Preserves folder hierarchy, wikilinks, and images, transforming Obsidian-specific syntax into Bugbook equivalents. Use when the user says "import obsidian", "migrate my vault", "import my notes from obsidian", or pastes an Obsidian vault path. Runs phases: pre-flight → inventory → transform plan (approval gate) → write → verify → report.

Pre-/go handoff check. Audits all To Do tickets for agent-readiness and writes machine-verifiable evals for each ticket. Use when the user says "prep", "prepare for go", "get ready for tonight", "am I ready for go", "check my tickets", "end of day", "audit the queue", or signals they're about to step away and want to make sure tickets are solid before autonomous execution. This is the bridge between interactive work and overnight execution.

Close the vision loop on SwiftUI work. Given a natural-language spec or reference image, this skill implements the change, builds Bugbook, drives the app to the target state, captures a real screenshot, and uses vision to compare against the spec — iterating until the UI matches. Use when the user says "make it look like this", "iterate until it matches", "screenshot this and compare", "pixel-match this design", or describes UI behavior that previously needed multiple rounds of human review to get right (expand/collapse, toggles, padding, layout). Especially useful for AppKit/SwiftUI subtleties like LazyVStack caching, NSScrollView constraints, or animation timing where Claude cannot reliably reason without visual feedback.

Create and execute single bug/feature tickets in Bugbook. Use when the user describes a bug, reports an issue, requests a feature, or says "ticket", "create a ticket", "log this", "file a bug". Also use when someone pastes an error, describes unexpected behavior, or asks to fix something specific. This is for single items — use /flow for batch workflows with multiple tickets.