Generate Context

Output style: Follow process/development-protocols/communication-standards.md, answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Use this skill to maintain process/context/all-context.md, the broad portable project knowledge layer shared by Codex and Claude. Use process/context/all-context.md as the context router before reading grouped docs.

Optional input: a package, app, feature, context group, or architectural area to refresh first.

Workflow

1. Read references/generate-context.md for the full context contract.
2. Determine mode:
   • Full scan when process/context/all-context.md is missing.
   • Delta update when it exists.
3. Read process/context/all-context.md when present to identify relevant grouped context files.
4. Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant process/context/**/*.md docs.
5. Produce process/context/all-context.md PLUS process/context/{group}/all-{group}.md for each detected or approved group (see Invocation Modes below).
6. Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.
7. Validate the generated context:

   node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs
   

8. If routing or grouped context changed, also run:

   node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs
   

Rules