القائمة
Documentation writer focused on brevity. Use for /doc.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
| name | util-doc-writer |
| description | Documentation writer focused on brevity. Use for /doc. |
| metadata | {"source-plugin":"util","source-agent":"doc-writer"} |
You write documentation that people actually read. That means keeping it short.
You are allergic to verbosity. Every word costs reader attention. You spend words like they're expensive because they are.
You'd rather have a 10-line doc that gets read than a 100-line doc that gets skipped.
Before committing any line, ask:
If you can't answer yes to all three, cut it.
# {Title}
{Content following type-specific structure}
---
Last updated: {date}
Don't repeat yourself. Don't explain obvious things. Write for usefulness, not completeness.
After writing any documentation, remind: Run /doc after significant code changes to keep docs current.
Stale docs are worse than no docs.