document-features
/document-features
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".
- Author
- thefrederiksen ↗
- Repository
- devthrottle ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author 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".
How it works
- Inputs and outputs
- Workflow
- Maintenance model
- Notes
SKILL.md preview
--- 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". --- # Document Features 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. ## Inputs and outputs | 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 | ## Workflow ### STEP 1: Inventory pass (decide what is implemented) 1. Read `docs/features/feature-inventory.yaml`. 2. Scan the UI source the way `/cencon-generate` reasons over the solution. Look in `src/CcDirector.Avalonia/` (views, `Controls/`, `*Dialog.axaml`) and `phone/CcDirectorClient/` (phone pages). 3. Reconcile: - A user-facing view/dialog that exists in source but is NOT in the inventory -> add it. - An inventory entry whose `source` file no longer exists -> remove it (or mark `planned`). - A surface that is stubbed (TODO / NotImplemented / framework-only) -> `partial`. 4. Keep every `source:` path repo-relative and real. Keep `id`s stable (they are the screenshot stems). ASCII only. 5. Report what changed (new / removed / status-changed features) before continuing. ### STEP 2: Capture pass (screenshot the running app) Run the harness: ```powershell powershell -NoProfile -ExecutionPolicy Bypass -File scripts/capture-feature-screenshots.ps1 ``` - It builds slot 5, launches via the `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. - Screens are captured with `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. - Run it from an INTERACTIVE desktop session. The main-window and tab shots work regardless, but the modal dialog shots (New Session, Settings) only render when the app can be foregrounded - a background/non-interactive run reports them as missing rather than capturing them. - Default dummy sessions are plain shells (`-Agent RawCli`) - no Claude subscription spent. Pass `-Agent ClaudeCode` when you need real agent output for the wingman/voice screens. - Read the harness summary. It prints which inventory screens were NOT auto-captured; those need either a new row in the script's `$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). ### STEP 3: Document pass (regenerate the pages) For each category in the inventory, update its page under `docs/public/features/`: - Embed each captured screenshot with a relative path: ``. - For a feature whose screenshot does not exist yet, write the text and add a line `_Screenshot pending - <how to capture it>._` instead of a broken image link. - Regenerate the feature matrix table in `01-overview.md` from the inventory (Feature | Status | Page). - Follow the writing style of the existing `docs/public/` pages: one-sentence intro, then the detail. No filler, no Unicode. ### STEP 4: Manifest pass 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. ### STEP 5: Report Summarize: features added/removed/changed status, screenshots refreshed, screens still pending. Do NOT commit unless the user explicitly asks (repo rule). ## Maintenance model - Re-run this skill before a release or whenever the README Features change. - The CI workflow `.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. ## Notes - Only touches `docs/features/`, `docs/public/features/`, `docs/public/index.json`, and the capture script. Never product code under `src/`. - The desktop window title cc-click matches is "CC Director". - If a required tool (cc-click, git, dotnet) is missing, the harness fails loudly with the fix - do not work around it. --- **Skill Version:** 1.0 **Last Updated:** 2026-06-19
Versions
The database has no other skills named document-features.
Database snapshot: 13.11.2026 · package version 43459f314941 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100update-docs
Update public documentation in docs/public/ when features or tools change. Triggers on "/update-docs", "update docs", "update documentation". - 100take-doc-screenshots
Take screenshots of the running pgconsole app for documentation. Use when updating docs with screenshots or adding images to .mdx files. - 100update-readme-screenshots
This skill should be used when the user asks to "update the README screenshots", "refresh the README", "regenerate the screenshots", "take new screenshots for the README", or "update the readme with new screenshots". Drives the Engy dev app with playwright-cli against seeded dev… - 100docs-audit-and-refresh
Audit the repository's docs/ content against the current codebase, find missing, incorrect, or stale documentation, and refresh the affected pages. Use when the user asks to review docs coverage, find outdated docs, compare docs with the current repo, or fix documentation drift… - 100product-docs-screenshots
Generate and refresh the screenshots in product-docs/ from a real, running CISO Assistant instance, and wire them into the Markdown. Use when: (1) User asks to illustrate, add screenshots to, or update a product-docs page (2) User ships a feature and asks to document it… - 100docs-refresh
Refresh documentation with deterministic generation from source files. Use when user says /docs-refresh.