Menu
Audit a repository's state and condense scattered notes into a phased ROADMAP.md. Invoke explicitly.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | audit-project |
| description | Audit a repository's state and condense scattered notes into a phased ROADMAP.md. Invoke explicitly. |
| argument-hint | [optional focus, e.g. 'test quality' or 'duplication'] |
| disable-model-invocation | true |
Take stock of a repo and turn whatever notes are lying around into a plan that
/orchestrate can execute. Optional focus: $ARGUMENTS.
This is read-and-write-one-file work. Do not start implementing.
Fan out with subagents; these are independent and each one would otherwise flood the conversation.
docs/ drafts, notes/, ADRs
without a decision, stale plan files under docs/**/plans/, commented-out code.Weigh candidates on what the user actually optimizes for: KISS, UX and DX, performance where it is measurable, and removing things over adding them. A phase that deletes code is worth as much as one that adds a feature.
Separate what is genuinely broken from what is merely unfinished, and both from what was abandoned on purpose. Say when something looks abandoned rather than assuming it is a gap.
Write to the repo root. Problem first, then what was considered, then the phased plan — lead the reader to the conclusion.
Phases are ordered by dependency, then by value. Each phase gets a one-line goal, the concrete work items, and how to tell it is done. Keep it reaction-sized; a roadmap nobody reads is worse than none.
Note explicitly what you decided to leave out and why.
Use AskUserQuestion on what the audit surfaced and the user has to decide: which phases matter, anything that looks abandoned and might just be deleted, and any fork you found where the repo could go two ways.
Do not commit. Do not begin implementing. Hand back the roadmap and the questions.
Write pull request review comments and replies to review threads in the user's voice. Use when reviewing a PR or diff and producing comments, when replying to a bot thread (CodeRabbit, Codex), when triaging or applying review findings, or when staging review feedback in a pr-<number>-review-comments.md file for the user to proofread before posting.
The user's full writing system for prose they author — README and docs text, landing copy, PR and commit descriptions, Linear proposals, design docs, Slack and email messages. Use when drafting or rewriting any human-facing prose, when a draft reads like AI wrote it, when stripping AI slop from documentation, or when relaying research output into a human-facing surface. CLAUDE.md carries the compressed rules; this carries the reasoning, the before/after pairs, and the per-format shapes.
incident.io assistant for working with incidents. View incident details, post updates to incident channels, interact with the incident agent, and query structured incident data. Use whenever the user mentions an incident ID (e.g., "INC-123"), asks about an incident, or uses the /incident command. Trigger proactively when you see an incident reference.
Freshens the repos listed in mani.yaml - syncs each with upstream, runs local gates, fixes CI on the default branch, and rolls template releases out to copier children. Arguments are a space-separated subset of repo names from mani.yaml; default is every repo.
On-demand UX critique for terminal UIs (Bubble Tea, Ratatui, Ink, Textual). Combines hyperskills:tui-design's layout/keybinding/color principles with impeccable's critique rigor (cognitive load, personas, heuristic scoring, P0-P3 severity), adapted for terminals — no CSS, no browser, no WCAG contrast math. Use when reviewing or critiquing a TUI's design, auditing keybinding discoverability, or checking terminal portability (NO_COLOR, monochrome degradation, multiplexer/SSH behavior).
Capture and persist browser screenshots or GIFs for visual review of a web UI. Use when verifying a UI change visually, reviewing a page's design or layout, recording a multi-step interaction (dropdown, hover, form flow), toggling dark mode for a comparison shot, or when a screenshot needs to be written to disk rather than only shown inline.