What problem does it solve? Research for software projects often scatters across ad-hoc notebooks, uncited web claims, and duplicated sources, making it hard to ground architecture and planning decisions in verifiable evidence. This Skill enforces exactly one curated NotebookLM notebook per project and turns bounded research into cited, local evidence packs that planning, Jules issues, and PR reviews can consume. ## Core Features & Use Cases - Single-notebook enforcement: Binds each project to one canonical NotebookLM notebook via an immutable local registry that refuses a second binding and validates source and evidence policies. - Curated source management: Organizes canonical, working, and evidence source classes with deduplication, redaction, a 60-source active limit, and a 20-source per-request import cap. - Research-to-delivery loop: Converts bounded research questions into a cited evidence pack with findings, recommendation, constraints, uncertainty, and provenance for plans and PR reviews. - Use Case: Before migrating a dependency, onboard the project to its canonical notebook, import up to 20 primary documentation sources, query for constraints, and hand the resulting evidence pack to the planning phase and the Jules issue. ## Quick Start Use $notebooklm-project-memory to bind this project to one NotebookLM notebook and prepare a cited evidence pack for the current decision.
