ferrox-docs-update

SkillDocs & knowledge

You want project documentation written or refreshed, checked against the actual code

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the ferrox-docs-update skill

What this skill tells your AI

The instructions your AI receives, as published by ferroxlabs/ferrox-factory in skills/ferrox-docs-update/SKILL.md and read by ahel’s review.

Flag handling rule:

The optional flags documented below are available behaviors, not implied active behaviors
A flag is active only when its literal token appears in $ARGUMENTS
If a documented flag is absent from $ARGUMENTS, treat it as inactive
--force: skip preservation prompts, regenerate all docs regardless of existing content or Ferrox markers
--verify-only: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)
If --force and --verify-only both appear in $ARGUMENTS, --force takes precedence

<execution_context> @~/.claude/ferrox-core/workflows/docs-update.md </execution_context>

Available optional flags (documentation only — not automatically active):

--force — Regenerate all docs. Overwrites hand-written and Ferrox 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 ferrox-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 $ARGUMENTS
If neither token appears, run the standard full-phase generation flow
Do not infer that a flag is active just because it is documented in this prompt

Advanced