← ClaudeAtlas

notes-processorlisted

Process and organize notes.md using the LNO (Leverage/Neutral/Overhead) framework for systematic task prioritization. Use when: (1) adding action items to notes.md, (2) organizing daily tasks, (3) categorizing work by ROI potential, (4) carrying forward incomplete tasks to new date sections, (5) routing brain-specific notes, (6) user requests "update notes" or "process my notes", or (7) synchronizing action items from CLAUDE.md files to daily tracking. Applies Shreyas Doshi's ROI-based prioritization framework to maintain strategic focus in daily execution.
samarv/Shanon · ★ 23 · AI & Automation · score 64
Install: claude install-skill samarv/Shanon
# Notes Processor Skill **Version**: 1.0.0 **Last Updated**: January 27, 2026 ## Purpose Systematically organize daily notes using the LNO framework to maintain strategic focus and ensure high-leverage work gets appropriate priority. This skill transforms ad-hoc note-taking into a strategic prioritization system that surfaces ROI-based work categorization. ## Invocation **Trigger phrases**: - "add action items to notes.md" - "update my notes" - "process notes" - "categorize these tasks" - "organize my daily tasks" - "sync action items from [brain]" **Usage**: ``` Invoked by agents (brain-tracker, meeting-notes-router) or directly when user requests notes organization ``` ## Framework: LNO Prioritization ### Core Philosophy **The Problem**: Not all work is equal. PMs often treat all tasks as equally important, leading to strategic work being crowded out by tactical firefighting. **The Solution**: Shreyas Doshi's LNO framework categorizes work by ROI potential: - **🟢 Leverage (L)**: 10x-100x ROI potential - Strategic initiatives, experiments, research - Documentation systems, templates, automation - Work that compounds over time - *Example*: "Design experiment to test new onboarding flow" - **🟡 Neutral (N)**: 1x ROI (equal effort to return) - Regular meetings, standard project work - Planning, coordination, reviews - Necessary but not amplifying - *Example*: "Weekly sync with engineering team" - **🔴 Overhead (O)**: <1x ROI (necessary but low retu