documenting-featureslisted

# Documenting Features Generate one Markdown file per feature, covering all 10 sections, written so Product can validate the first half and Engineering can maintain the whole thing. Lives next to the code, version-controlled, kept in sync with implementation. ## Read first (always) List `learnings/` and read every file relevant to the current feature (the domain, the bounded context, the team). Project-specific naming conventions, ADR numbering, glossary inheritance rules, or template variants live there and override the defaults in this SKILL.md. If a learning conflicts with this file, **the learning wins** — mention it to the user. ## Tradeoff — when to apply, when to lighten up Apply the full 10-section template for **shipped features** that cross team boundaries (Product ↔ Engineering ↔ Ops) or touch the domain model. Lighten formality (skip sections, not principles) for: internal tooling not exposed to users; refactors with no behavior change (document the ADR only); spike work and prototypes behind feature flags. Never skip Section 1 (Overview) and Section 2 (Ubiquitous Language) — the glossary is the single source of truth for cross-team communication. ## Core principles 1. **Ubiquitous language is the single source of truth.** The same term across docs, code, database, and conversation. If the business calls it "Enrollment", the code has `class Enrollment` and the database has the `enrollments` table — no synonyms. 2. **Documentation lives next to the code.**