rcode-document-projectlisted

<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. --> @.rcode/references/karpathy-guidelines.md ## Overview Analyze an existing codebase and produce documentation for both human and LLM consumption (brownfield analysis). ## Workflow Follow the instructions in ./workflow.md. ## When NOT to use this skill Do NOT use for writing net-new documentation from scratch (use a write-document prompt). Do NOT invoke when the user wants to document a single file or function — scope this skill to whole-codebase or whole-module brownfield analysis only. ## Output Format - Produces multi-file documentation: README summary, ARCHITECTURE.md, CONVENTIONS.md, project-context.md - Scans code to detect actual patterns (not what docs claim) - Do NOT fabricate patterns not present in code - Do NOT skip sections — if data is missing, flag it explicitly ## Examples ### Happy Path **Input:** "Document this repo" **Expected behavior:** Scan repo structure, detect stack, identify patterns, produce multi-file docs with actual findings. ### Edge Case: Inconsistent Patterns **Input:** (codebase has multiple competing patterns) **Expected behavior:** Document each pattern with location and flag the inconsistency for the team to resolve.