菜单
Generate and refresh the public feature documentation in docs/public/features/ - scan the code to decide what is implemented, screenshot the running app, and update the pages. Triggers on "/document-features", "document the features", "refresh feature screenshots", "regenerate feature docs".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | document-features |
| description | Generate and refresh the public feature documentation in docs/public/features/ - scan the code to decide what is implemented, screenshot the running app, and update the pages. Triggers on "/document-features", "document the features", "refresh feature screenshots", "regenerate feature docs". |
Keep docs/public/features/ and its screenshots in sync with the app. This is the
"docs-as-code with regenerated screenshots" pipeline: the inventory is decided from
source, the screenshots are captured from a real (throwaway) build, and the pages
are regenerated together. Re-run after UI changes - never hand-edit screenshots.
| Artifact | Role |
|---|---|
docs/features/feature-inventory.yaml | Source-of-truth: each feature, its status, and the file that proves it exists |
scripts/capture-feature-screenshots.ps1 | Launches a slot build, makes dummy sessions, screenshots each screen |
docs/public/features/*.md | The published pages (raw markdown on GitHub) |
docs/public/features/assets/*.png | Committed screenshots referenced by the pages |
docs/public/index.json | Manifest listing every page |
docs/features/feature-inventory.yaml./cencon-generate reasons over the solution. Look in
src/CcDirector.Avalonia/ (views, Controls/, *Dialog.axaml) and
phone/CcDirectorClient/ (phone pages).source file no longer exists -> remove it (or mark planned).partial.source: path repo-relative and real. Keep ids stable (they are the
screenshot stems). ASCII only.Run the harness:
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/capture-feature-screenshots.ps1
cc-director-launch scheduled task (per
CLAUDE.md - never spawn the app from this process tree for session-creating runs),
creates dummy sessions, captures the shots, and tears down ONLY slot 5.cc-click screenshot --pid <slot pid>, which uses
Win32 PrintWindow to grab OUR window's own pixels - occlusion-proof, so it can
never accidentally capture one of the user's other CC Director windows.-Agent RawCli) - no Claude subscription
spent. Pass -Agent ClaudeCode when you need real agent output for the
wingman/voice screens.$Shots table or a manual capture.To extend automated coverage, add a row to $Shots in the harness (each row is a
screenshot name plus the cc-click navigation to reach that screen).
For each category in the inventory, update its page under docs/public/features/:
._Screenshot pending - <how to capture it>._ instead of a broken image link.01-overview.md from the inventory
(Feature | Status | Page).docs/public/ pages: one-sentence intro,
then the detail. No filler, no Unicode.Update docs/public/index.json so every page under docs/public/features/ has an
entry in the features category. Validate (same rules as /update-docs): every
file points at a real file, every page is listed, ids are lowercase-kebab-case.
Summarize: features added/removed/changed status, screenshots refreshed, screens still pending. Do NOT commit unless the user explicitly asks (repo rule).
.github/workflows/docs-drift.yml runs only STEP 1's reconcile
(no GUI) on pull requests and flags when the inventory is stale relative to source.
It cannot screenshot a desktop GUI on a headless runner - it only nudges a human to
re-run the full local pass.docs/features/, docs/public/features/, docs/public/index.json,
and the capture script. Never product code under src/.Skill Version: 1.0 Last Updated: 2026-06-19
Relocate a live session to another cc-director slot or Director - approval-gated handover through the GATEWAY, the seed identifies itself as a moved session, the TARGET keeps the source's original name, the source is renamed "[MOVED]" and put on hold so the user can close it. Triggers on "/move-session", "move session", "migrate session", "transfer session".
INTERNAL reference, NOT shipped with the installer. The in-repo expert on every coding-agent CLI CC Director can run (Claude Code, Codex, Gemini, OpenCode, Grok, Copilot, Cursor, Pi). Knows each agent's command line, config files, context-injection points, lifecycle hooks and events, SDK/API/server mode, transcript format, session semantics, and how CC Director drives it. Triggers on "agent-expert", "agent expert", "how does <agent> inject context", "<agent> hooks", "<agent> events", "<agent> CLI reference", "which agents support X", "agent capability matrix".
How a mission is RUN in this repository - the Architect, the Manager, the Workers, and the independent Inspector, plus the four standing laws (ask up front then run alone, and NEVER guess - bring the owner in when something is genuinely undecidable; the mission branch holds the work and only the Architect lands it on main; a different agent family inspects before anything reaches main; merged to origin/main is the only done). Read this BEFORE starting or seeding any mission, and before writing any mission brief. Triggers on "/mission", "start a mission", "run a mission", "seed an architect", "write a mission brief", "mission brief", "who merges", "mission roles".
DevThrottle - "Mission Control for Claude Code". A desktop app (binary cc-director.exe) that runs and supervises multiple Claude Code sessions and ships cc-* CLI tools on PATH. Agents drive the fleet through the cc-devthrottle command, not by calling the Director over HTTP. Triggers on "/dev-throttle", "/devthrottle", "/cc-director", "what cc tools", "list tools", "available tools", "devthrottle api", "session manager", "mission control".
Talk to other DevThrottle sessions across the fleet. Use when you want to list running sessions, rename this session, message another session, ask another session a question and get its answer, or open a new session - from inside a session. Triggers on "/fleet-comms", "message another session", "talk to another session", "ask another session", "rename this session", "rename session", "list sessions", "what sessions are running", "open a session", "spawn a session", "cc-devthrottle", "fleet messaging", "session intercommunication".
Guided run-book for cutting a DevThrottle release - assemble the changes, write the release notes, coordinate the internal docs site, cut the tag, and announce it. Triggers on "/release-manager", "cut a release", "prepare a release", "ship a release", "do the release".