Generate or update up to nine project documentation files using direct inspection of the codebase. Check existing documents against the implementation, preserve content through workflow checks, or explicitly request full regeneration.
Generate or update project documentation verified against the codebase
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Flag handling rule:
$ARGUMENTS$ARGUMENTS, treat it as inactive--force: skip preservation prompts, regenerate all docs regardless of existing content or GSD markers--verify-only: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)--force and --verify-only both appear in $ARGUMENTS, --force takes precedence
</objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/docs-update.md </execution_context>
<context> Arguments: $ARGUMENTSAvailable optional flags (documentation only — not automatically active):
--force — Regenerate all docs. Overwrites hand-written and GSD docs alike. No preservation prompts.--verify-only — Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the gsd-doc-verifier agent (Phase 4).Active flags must be derived from $ARGUMENTS:
--force is active only if the literal --force token is present in $ARGUMENTS--verify-only is active only if the literal --verify-only token is present in $ARGUMENTSNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.
Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.
Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.
Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.
Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.
Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.