skills

Quickly get back up to speed on where this session stands and what matters now.

On-point grill of any doc, plan, or rough idea with the grill-with-docs skill — only high-value findings reach me.

Defines where spec-driven working artifacts — the spec (e.g. `SPEC.md`), the plan, and the task list (e.g. `tasks/plan.md`, `tasks/todo.md`) — live on disk under `docs/specs/<id>-<slug>/`, and how those directories are numbered, scoped, and resolved so multiple specs can run in parallel without overwriting one another. Use this BEFORE creating, locating, or updating any spec, plan, or task/todo file — whenever a spec/plan/build workflow writes these artifacts, whenever you need to find the right feature directory to act on, when more than one spec or feature is in progress at once, or when a draft spec gets a tracker issue number assigned. Trigger even if only one spec exists and even if the user never mentions where the file should go. Governs only where artifacts live and how they are addressed, not what content goes in them.

Find branch coverage gaps in changed code and fix them by writing missing tests. Two analysis layers: Source ↔ Test (logic branches vs test cases) and Spec ↔ Test (requirement scenarios vs test cases, when a spec file is provided). Use when verifying test completeness after implementing a feature or fixing a bug, when auditing whether tests match a spec, or when suspecting untested branches.

Rewrite a piece of text down to its core message, dropping whatever is peripheral to it — the result is the text itself rewritten shorter, not a summary written about it. Use when the user explicitly asks to distil, cut to the essentials, trim the fat, or strip a passage, document, or draft down to what matters, and is willing to lose secondary detail. Do not trigger as unprompted cleanup of text the user has not asked to change; when the user wants the text shorter but every point kept, use the tighten skill instead.

Decode Zhuyin (Bopomofo) text typed with English keyboard keys into Chinese characters. ALWAYS try this skill when encountering unrecognized short letter/number sequences mixed with Chinese text that don't look like real English words or acronyms - e.g. "e04", "cl3", "su3", "cp3". Also use when user explicitly mentions 注音文, or asks what a cryptic alphanumeric fragment means in a Chinese context.

Before acting on an approval, re-read from disk every file that was under review — the user may have edited them while reviewing, leaving your in-context copy stale. Use when the user signals go-ahead on something you put up for review — "lgtm", "looks good", "looks good to me", "approved", "go ahead" — before you start the next step. Applies to any reviewed artifact — spec, plan, diff, edited code, proposal.

2 hooks across 2 events