What problem does it solve? Design context, deferred decisions, and cross-cutting implementation contracts often get lost between conversations because they don't warrant a full research spike or tech spec. This Skill gives that working knowledge a persistent, well-placed home in the docs tree. ## Core Features & Use Cases - Scope resolution: Automatically determines whether a note belongs to a project (docs/xNNN-<name>/notes/) or the global scope (docs/notes/), asking once when ambiguous. - Name normalization: Converts titles like OAuth/PKCE notes! into clean kebab-case filenames such as oauth-pkce-notes. - CLI-based scaffolding: Delegates file creation to the yolo new note scaffold CLI, parsing its JSON envelope for the created path and surfacing structured errors like collision or missing-project. - Use Case: While designing an auth flow you discover an unresolved decision about channel outbox ownership. Invoke the skill to scaffold channel-outbox-ownership.md in the current project's notes directory, then fill in the Core Questions and Scope sections. ## Quick Start Ask the assistant to create a note named channel-outbox-ownership capturing the deferred decision about message delivery ownership in the current project.
