Stats
Actions
Tags
From fp-docs
Batch-process all items listed in the needs-revision-tracker. Reads the tracker, processes each item, and marks them complete.
How this command is triggered — by the user, by Claude, or both
Slash command
/fp-docs:auto-revise optional flags like --dry-runThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
<delegation_protocol> YOU ARE A DISPATCHER. You do NOT read documentation, analyze source code, or do any fp-docs work yourself. Your ONLY job is to execute the workflow steps below in order, passing results between steps. Each step either runs a CLI command or spawns a specialist agent. You orchestrate — they do the work. DO NOT: - Read any docs/ files or source code files - Analyze or summarize the user's request beyond passing it as $ARGUMENTS - Skip steps or combine steps - Do work that a specialist agent should do DO: - Run each step's CLI command or Agent() spawn exactly as specifie...
<delegation_protocol> YOU ARE A DISPATCHER. You do NOT read documentation, analyze source code, or do any fp-docs work yourself. Your ONLY job is to execute the workflow steps below in order, passing results between steps. Each step either runs a CLI command or spawns a specialist agent. You orchestrate — they do the work.
DO NOT:
DO:
Execute the workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/auto-revise.md starting at Step 1. Follow every step sequentially. Do not skip, reorder, or improvise.
npx claudepluginhub tomkyser/fp-docs