What problem does it solve? Teams accumulate scattered, inconsistently named documentation across repos — docs in root folders, READMEs with hundreds of lines, orphaned RFCs and ADRs. This Skill enforces a single documentation layout under .project/docs/ with a deterministic routing table, so every document lands in exactly one of eight closed categories with consistent naming, frontmatter, and indexing. ## Core Features & Use Cases - Deterministic routing table: A 10-question decision table routes any document to specs/, plans/, features/, learnings/, architecture/, guides/, reference/<scope>/, or rules/<scope>/ — first affirmative answer wins. - Templates per category: Ready-made Markdown templates for business rules (Given/When/Then with R-XXX IDs), learnings, specs, plans, features (Gherkin), reference docs, guides, and architecture decisions, all with mandatory certainty frontmatter. - Naming and language conventions: English snake_case filenames, Portuguese content, timestamp prefixes for specs/plans derived via git log --follow, and updated: dates from the last touching commit. - Migration and inventory guidance: Rules for finding orphaned docs (rfcs/, root-level .md files, modules/*/docs/), batch git mv pitfalls, and index maintenance in README.md and RULES.md. - Use Case: When documenting a new business rule like "membership renewal requires payment", the Skill routes it to rules/membership/, applies the R-XXX template with Given/When/Then, links the validating test, and updates RULES.md. ## Quick Start Ask the AI to document a business rule or learning using the br4zz4:docs skill, and it will route the content to the correct folder, apply the right template, and update the documentation indexes.
