Run any Skill in Manus with one click

review-docs

Stars3

Forks0

UpdatedApril 25, 2026 at 20:12

Scan docs/ for plans, tickets, research, brainstorms, and decisions, then display them organized by topic. Shows open vs archived counts, item types, and priorities. Use when you want a project overview, need to find existing work, or want to see what's planned. Triggers on "review docs", "show docs", "what's planned", "project overview", "list tickets", "list plans", "docs overview".

Installation

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.

Run Skill in Manus

Source

proteus-computer-use

proteus-computer-use/screencap

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	review-docs
description	Scan docs/ for plans, tickets, research, brainstorms, and decisions, then display them organized by topic. Shows open vs archived counts, item types, and priorities. Use when you want a project overview, need to find existing work, or want to see what's planned. Triggers on "review docs", "show docs", "what's planned", "project overview", "list tickets", "list plans", "docs overview".

Review Docs by Topic

Scan docs/ for all plans, tickets, research, brainstorms, and decisions, then present them organized by topic with counts and status.

Instructions

Step 1: Scan Each Topic Directory

Scan these top-level directories under docs/:

tickets/ — open tickets
plans/ — open plans
research/ — research docs
brainstorms/ — open brainstorms
decisions/ — cross-cutting ADRs
tickets/archived/ — archived tickets
plans/archived/ — archived plans
brainstorms/archived/ — archived brainstorms

Count files in each. For open items, extract the filename to show as a list item.

docs/solutions/ and docs/todos/ are also valid topic directories — include them only if the user asks (/review-docs solutions, /review-docs todos).

Step 2: Parse Priority from Filenames

Tickets may have priority prefixes in their filenames:

urgent- prefix → URGENT
high- prefix → HIGH
No prefix → normal

Flag urgent and high items prominently in the output.

Step 3: Check for Args

Handle optional filtering:

/review-docs — full overview across all topics
/review-docs tickets — show only tickets
/review-docs plans — show only plans
/review-docs research — show only research
/review-docs brainstorms — show only brainstorms
/review-docs decisions — show only decisions
/review-docs archived — show only archived items across all topics

Step 4: Render Output

Present a structured summary grouped by topic. Format:

## Project Docs Overview

### Tickets
Open: N (X urgent, Y high, Z medium, W low, V unset)
Archived: M

**URGENT** `urgent-2026-03-05-fix-pii-false-positives-in-accessibility-text.md`
**HIGH** `high-2026-03-07-audio-no-redaction.md`
**HIGH** `high-2026-03-07-video-no-redaction.md`

Open tickets:
- fix-screenshot-ocr-pii-false-positives (2026-03-05)
- feat-browser-url-via-accessibility-api (2026-03-06)
- feat-scrubbed-copy-auto-export (2026-02-24)
- ...

---

### Plans
Open: N
Archived: M

Open plans:
- fix-scrub-audit-and-hardening (2026-03-03)
- feat-screenshot-image-redaction (2026-03-05)
- ...

---

### Research
Total: N

- redaction-gap-analysis (2026-03-07)
- chatgpt-secret-redaction-deep-research (undated)
- ...

---

### Brainstorms
Open: N
Archived: M

Open brainstorms:
- ...

---

### Decisions
ADRs in `docs/decisions/` — project-wide cross-cutting decisions:
- 001 — Variable-rate capture over dedup gating
- 002 — Disable dhash by default
- 003 — Upload screenshots only, video local
- 004 — No pixel comparison for frame drops

---

### Summary
Total open: X tickets, Y plans, Z research, W brainstorms
Total archived: M items
Decisions: D ADRs

Formatting Rules

Within tickets, show urgent/high items first, then the rest sorted newest-first
For each item, strip the date prefix and -plan/-brainstorm suffix to show a human-readable name
Show the date in parentheses
Topics with no items: show the counts line but skip the item list
Use --- separators between topics for readability

Step 5: Offer Follow-up

After showing the overview, offer:

Want me to:
- Read a specific doc? (give the filename)
- Show archived items?
- Create a new ticket or plan?

More from this repository

same repository

macos-app-release

proteus-computer-use/screencap

Build, sign, notarize, and publish a new macOS ScreenCap.app release (.dmg). Bumps the app version, builds the embedded daemon with PyInstaller, builds the app with Xcode, Developer-ID signs + notarizes + staples, packages a DMG, tags `macos-app-vX.Y.Z`, and creates a GitHub prerelease. This is the app track — distinct from `local-release` (the headless CLI/`vX.Y.Z` track). Triggers on "release the macOS app", "new app release", "build a new DMG", "ship the app to testers", or after Swift/UI or embedded-daemon changes land.

2026-07-093

local-release

proteus-computer-use/screencap

Bump version, build, and release screencap locally. Mirrors the /release flow (version bump, changelog, commit, tag, push) but builds locally instead of triggering GH Actions. Supports arm64 (native on Apple Silicon), x86_64 (requires python.org universal2 Python 3.12 + Rosetta), and both. Use when CI is unavailable (billing limits, runner outages). Triggers on "local release", "release locally", "build and release", or when CI release fails.

2026-07-023

next-ticket

proteus-computer-use/screencap

Pick the highest-priority ready-to-start Linear ticket on the Screencap team, claim it (assign + move to In Progress / Planning), and hand off into the right Compound Engineering skill (ce-debug / ce-work / ce-plan) primed with the ticket. Flags too-thin tickets with needs-info instead of starting them. Use when you want to start the next piece of work without manually triaging the backlog. Triggers on "next ticket", "what's next", "pick a ticket", "pick the next ticket", "start next work", "grab a ticket", "work the next ticket".

2026-06-183

capture-test

proteus-computer-use/screencap

End-to-end capture pipeline sanity check. Runs a real screencap recording, asks the user to perform actions, then validates the captured data (files, DB, screenshots). Use when testing capture changes, verifying the recording pipeline works, or after modifying recorder/catalog code. Triggers on "test capture", "capture test", "sanity check", "test recording pipeline", or after changes to recorder.py, catalog.py, or screencap.engine.

2026-04-263

list-tickets

proteus-computer-use/screencap

List all open tickets with status and priority. Shows what's pending, in-progress, blocked, or planned. Sorted by priority (urgent > high > medium > low > unset). Use when you want to see the ticket backlog, check what's blocked, find work to do, or get a status overview. Triggers on "list tickets", "ticket status", "what's open", "what needs work", "backlog", "show tickets", "ticket overview", "what's blocked".

2026-04-253

compound

proteus-computer-use/screencap

Document a solved problem, completed feature, porting decision, or architecture learning to compound team knowledge. Auto-triggers on "that worked", "it's fixed", "feature complete", "porting done". Creates one MD file per item in docs/solutions/[category]/. Use after research, planning, implementation, or debugging sessions.

2026-03-213

name	review-docs
description	Scan docs/ for plans, tickets, research, brainstorms, and decisions, then display them organized by topic. Shows open vs archived counts, item types, and priorities. Use when you want a project overview, need to find existing work, or want to see what's planned. Triggers on "review docs", "show docs", "what's planned", "project overview", "list tickets", "list plans", "docs overview".

Review Docs by Topic

Scan docs/ for all plans, tickets, research, brainstorms, and decisions, then present them organized by topic with counts and status.

Instructions

Step 1: Scan Each Topic Directory

Scan these top-level directories under docs/:

tickets/ — open tickets
plans/ — open plans
research/ — research docs
brainstorms/ — open brainstorms
decisions/ — cross-cutting ADRs
tickets/archived/ — archived tickets
plans/archived/ — archived plans
brainstorms/archived/ — archived brainstorms

Count files in each. For open items, extract the filename to show as a list item.

docs/solutions/ and docs/todos/ are also valid topic directories — include them only if the user asks (/review-docs solutions, /review-docs todos).

Step 2: Parse Priority from Filenames

Tickets may have priority prefixes in their filenames:

urgent- prefix → URGENT
high- prefix → HIGH
No prefix → normal

Flag urgent and high items prominently in the output.

Step 3: Check for Args

Handle optional filtering:

/review-docs — full overview across all topics
/review-docs tickets — show only tickets
/review-docs plans — show only plans
/review-docs research — show only research
/review-docs brainstorms — show only brainstorms
/review-docs decisions — show only decisions
/review-docs archived — show only archived items across all topics

Step 4: Render Output

Present a structured summary grouped by topic. Format:

## Project Docs Overview

### Tickets
Open: N (X urgent, Y high, Z medium, W low, V unset)
Archived: M

**URGENT** `urgent-2026-03-05-fix-pii-false-positives-in-accessibility-text.md`
**HIGH** `high-2026-03-07-audio-no-redaction.md`
**HIGH** `high-2026-03-07-video-no-redaction.md`

Open tickets:
- fix-screenshot-ocr-pii-false-positives (2026-03-05)
- feat-browser-url-via-accessibility-api (2026-03-06)
- feat-scrubbed-copy-auto-export (2026-02-24)
- ...

---

### Plans
Open: N
Archived: M

Open plans:
- fix-scrub-audit-and-hardening (2026-03-03)
- feat-screenshot-image-redaction (2026-03-05)
- ...

---

### Research
Total: N

- redaction-gap-analysis (2026-03-07)
- chatgpt-secret-redaction-deep-research (undated)
- ...

---

### Brainstorms
Open: N
Archived: M

Open brainstorms:
- ...

---

### Decisions
ADRs in `docs/decisions/` — project-wide cross-cutting decisions:
- 001 — Variable-rate capture over dedup gating
- 002 — Disable dhash by default
- 003 — Upload screenshots only, video local
- 004 — No pixel comparison for frame drops

---

### Summary
Total open: X tickets, Y plans, Z research, W brainstorms
Total archived: M items
Decisions: D ADRs

Formatting Rules

Within tickets, show urgent/high items first, then the rest sorted newest-first
For each item, strip the date prefix and -plan/-brainstorm suffix to show a human-readable name
Show the date in parentheses
Topics with no items: show the counts line but skip the item list
Use --- separators between topics for readability

Step 5: Offer Follow-up

After showing the overview, offer:

Want me to:
- Read a specific doc? (give the filename)
- Show archived items?
- Create a new ticket or plan?