What problem does it solve? Project knowledge lives scattered across calls, message threads, and screens nobody will revisit, so every contractor briefing or AI session starts with re-explaining context. This Skill ingests one project's captured meetings, threads, and on-screen artifacts and writes a durable markdown documentation pack with receipts on every fact. ## Core Features & Use Cases - Structured documentation pack: Produces an index, glossary, product requirements, architecture notes, decision records (MADR, Nygard, or Y-statement), a brand brief, and an open questions register in a numbered directory. - Contradiction register: Detects six kinds of conflicts (numeric, reversal, definitional, scope, attribution, temporal) and records both readings with dates and receipts, resolved through a confirmation gate. - Sensitive segregation: Sorts financial, legal, equity, personnel, and third-party confidential material into a separate file before any document is written. - Monthly staleness watch: Optionally creates a Littlebird routine that flags stale documents, new decisions, and unresolved contradictions, then hands back to an interactive session. - Use Case: Ask it to document a project before briefing a contractor, and receive a complete pack where every requirement carries a receipt and every conflict is surfaced rather than silently resolved. ## Quick Start Ask the assistant to build a knowledge base for your project from your recorded calls and threads, then answer the four scoping questions about the project's names, calls, people, and purpose.
