commit 1ba2d7644eba2304503657afb41abfb4abeee501 Author: zlei9 Date: Sun Mar 29 10:14:09 2026 +0800 Initial commit with translated description diff --git a/SKILL.md b/SKILL.md new file mode 100644 index 0000000..da50c8c --- /dev/null +++ b/SKILL.md @@ -0,0 +1,255 @@ +--- +name: Productivity +slug: productivity +version: 1.0.4 +homepage: https://clawic.com/skills/productivity +description: "通过能量管理、时间块、目标、项目、任务、习惯、回顾、优先级和特定情境生产力系统来计划、专注和完成工作。" +changelog: Expanded the system with clearer routing, setup, and folders for goals, tasks, habits, planning, and reviews +metadata: {"clawdbot":{"emoji":"⚡","requires":{"bins":[]},"os":["linux","darwin","win32"],"configPaths":["~/productivity/"]}} +--- + +## When to Use + +Use this skill when the user wants a real productivity system, not just one-off motivation. It should cover goals, projects, tasks, habits, planning, reviews, overload triage, and situation-specific constraints in one coherent operating model. + +## Architecture + +Productivity lives in `~/productivity/`. If `~/productivity/` does not exist yet, run `setup.md`. + +``` +~/productivity/ +├── memory.md # Work style, constraints, energy, preferences +├── inbox/ +│ ├── capture.md # Quick capture before sorting +│ └── triage.md # Triage rules and current intake +├── dashboard.md # High-level direction and current focus +├── goals/ +│ ├── active.md # Outcome goals and milestones +│ └── someday.md # Goals not committed yet +├── projects/ +│ ├── active.md # In-flight projects +│ └── waiting.md # Blocked or delegated projects +├── tasks/ +│ ├── next-actions.md # Concrete next steps +│ ├── this-week.md # This week's commitments +│ ├── waiting.md # Waiting-for items +│ └── done.md # Completed items worth keeping +├── habits/ +│ ├── active.md # Current habits and streak intent +│ └── friction.md # Things that break consistency +├── planning/ +│ ├── daily.md # Daily focus and must-win +│ ├── weekly.md # Weekly plan and protected time +│ └── focus-blocks.md # Deep work and recovery blocks +├── reviews/ +│ ├── weekly.md # Weekly reset +│ └── monthly.md # Monthly reflection and adjustments +├── commitments/ +│ ├── promises.md # Commitments made to self or others +│ └── delegated.md # Handed-off work to track +├── focus/ +│ ├── sessions.md # Deep work sessions and patterns +│ └── distractions.md # Repeating focus breakers +├── routines/ +│ ├── morning.md # Startup routine and first-hour defaults +│ └── shutdown.md # End-of-day reset and carry-over logic +└── someday/ + └── ideas.md # Parked ideas and optional opportunities +``` + +The skill should treat this as the user's productivity operating system: one trusted place for direction, commitments, execution, habits, and periodic review. + +## Quick Reference + +| Topic | File | +|-------|------| +| Setup and routing | `setup.md` | +| Memory structure | `memory-template.md` | +| Productivity system template | `system-template.md` | +| Cross-situation frameworks | `frameworks.md` | +| Common mistakes | `traps.md` | +| Student context | `situations/student.md` | +| Executive context | `situations/executive.md` | +| Freelancer context | `situations/freelancer.md` | +| Parent context | `situations/parent.md` | +| Creative context | `situations/creative.md` | +| Burnout context | `situations/burnout.md` | +| Entrepreneur context | `situations/entrepreneur.md` | +| ADHD context | `situations/adhd.md` | +| Remote work context | `situations/remote.md` | +| Manager context | `situations/manager.md` | +| Habit context | `situations/habits.md` | +| Guilt and recovery context | `situations/guilt.md` | + +## What This Skill Sets Up + +| Layer | Purpose | Default location | +|-------|---------|------------------| +| Capture | Catch loose inputs fast | `~/productivity/inbox/` | +| Direction | Goals and active bets | `~/productivity/dashboard.md` + `goals/` | +| Execution | Next actions and commitments | `~/productivity/tasks/` | +| Projects | Active and waiting project state | `~/productivity/projects/` | +| Habits | Repeated behaviors and friction | `~/productivity/habits/` | +| Planning | Daily, weekly, and focus planning | `~/productivity/planning/` | +| Reflection | Weekly and monthly reset | `~/productivity/reviews/` | +| Commitments | Promises and delegated follow-through | `~/productivity/commitments/` | +| Focus | Deep work protection and distraction logs | `~/productivity/focus/` | +| Routines | Startup and shutdown defaults | `~/productivity/routines/` | +| Parking lot | Non-committed ideas | `~/productivity/someday/` | +| Personal fit | Constraints, energy, preferences | `~/productivity/memory.md` | + +This skill should give the user a single framework that can absorb: +- goals +- projects +- tasks +- habits +- priorities +- focus sessions +- routines +- focus blocks +- reviews +- commitments +- inbox capture +- parked ideas +- bottlenecks +- context-specific adjustments + +## Quick Queries + +| User says | Action | +|-----------|--------| +| "Set up my productivity system" | Create the `~/productivity/` baseline and explain the folders | +| "What should I focus on?" | Check dashboard + tasks + commitments + focus, then surface top priorities | +| "Help me plan my week" | Use goals, projects, commitments, routines, and energy patterns to build a weekly plan | +| "I'm overwhelmed" | Triage commitments, cut scope, and reset next actions | +| "Turn this goal into a plan" | Convert goal -> project -> milestones -> next actions | +| "Do a weekly review" | Update wins, blockers, carry-overs, and next-week focus | +| "Help me with habits" | Use `habits/` to track what to keep, drop, or redesign | +| "Help me reset my routine" | Use `routines/` and `planning/` to simplify startup and shutdown loops | +| "Remember this preference" | Save it to `~/productivity/memory.md` after explicit confirmation | + +## Core Rules + +### 1. Build One System, Not Five Competing Ones +- Prefer one trusted productivity structure over scattered notes, random task lists, and duplicated plans. +- Route goals, projects, tasks, habits, routines, focus, planning, and reviews into the right folder instead of inventing a fresh system each time. +- If the user already has a good system, adapt to it rather than replacing it for style reasons. + +### 2. Start With the Real Bottleneck +- Diagnose whether the problem is priorities, overload, unclear next actions, bad estimates, weak boundaries, or low energy. +- Give the smallest useful intervention first. +- Do not prescribe a full life overhaul when the user really needs a clearer next step. + +### 3. Separate Goals, Projects, and Tasks Deliberately +- Goals describe outcomes. +- Projects package the work needed to reach an outcome. +- Tasks are the next visible actions. +- Habits are repeated behaviors that support the system over time. +- Never leave a goal sitting as a vague wish without a concrete project or next action. + +### 4. Adapt the System to Real Constraints +- Use the situation guides when the user's reality matters more than generic advice. +- Energy, childcare, deadlines, meetings, burnout, and ADHD constraints should shape the plan. +- A sustainable system beats an idealized one that collapses after two days. + +### 5. Reviews Matter More Than Constant Replanning +- Weekly review is where the system regains trust. +- Clear stale tasks, rename vague items, and reconnect tasks to real priorities. +- If the user keeps replanning daily without progress, simplify and review instead. + +### 6. Save Only Explicitly Approved Preferences +- Store work-style information only when the user explicitly asks you to save it or clearly approves. +- Before writing to `~/productivity/memory.md`, ask for confirmation. +- Never infer long-term preferences from silence, patterns, or one-off comments. + +## Common Traps + +- Giving motivational talk when the problem is actually structural. +- Treating every task like equal priority. +- Mixing goals, projects, and tasks in the same vague list. +- Building a perfect system the user will never maintain. +- Recommending routines that ignore the user's real context. +- Preserving stale commitments because deleting them feels uncomfortable. + +## Scope + +This skill ONLY: +- builds or improves a local productivity operating system +- gives productivity advice and planning frameworks +- reads included reference files for context-specific guidance +- writes to `~/productivity/` only after explicit user approval + +This skill NEVER: +- accesses calendar, email, contacts, or external services by itself +- monitors or tracks behavior in the background +- infers long-term preferences from observation alone +- writes files without explicit user confirmation +- makes network requests +- modifies its own SKILL.md or auxiliary files + +## External Endpoints + +This skill makes NO external network requests. + +| Endpoint | Data Sent | Purpose | +|----------|-----------|---------| +| None | None | N/A | + +No data is sent externally. + +## Data Storage + +Local files live in `~/productivity/`. + +- `~/productivity/memory.md` stores approved preferences, constraints, and work-style notes +- `~/productivity/inbox/` stores fast captures and triage +- `~/productivity/dashboard.md` stores top-level direction and current focus +- `~/productivity/goals/` stores active and someday goals +- `~/productivity/projects/` stores active and waiting projects +- `~/productivity/tasks/` stores next actions, weekly commitments, waiting items, and completions +- `~/productivity/habits/` stores active habits and friction notes +- `~/productivity/planning/` stores daily plans, weekly plans, and focus blocks +- `~/productivity/reviews/` stores weekly and monthly reviews +- `~/productivity/commitments/` stores promises and delegated follow-through +- `~/productivity/focus/` stores deep-work sessions and distraction patterns +- `~/productivity/routines/` stores startup and shutdown defaults +- `~/productivity/someday/` stores parked ideas + +Create or update these files only after the user confirms they want the system written locally. + +## Migration + +If upgrading from an older version, see `migration.md` before restructuring any existing `~/productivity/` files. +Keep legacy files until the user confirms the new system is working for them. + +## Security & Privacy + +**Data that leaves your machine:** +- Nothing. This skill performs no network calls. + +**Data stored locally:** +- Only the productivity files the user explicitly approves in `~/productivity/` +- Work preferences, constraints, priorities, and planning artifacts the user chose to save + +**This skill does NOT:** +- access internet or third-party services +- read calendar, email, contacts, or system data automatically +- run scripts or commands by itself +- monitor behavior in the background +- infer hidden preferences from passive observation + +## Trust + +This skill is instruction-only. It provides a local framework for productivity planning, prioritization, and review. Install it only if you are comfortable storing your own productivity notes in plain text under `~/productivity/`. + +## Related Skills +Install with `clawhub install ` if user confirms: +- `self-improving` — Compound execution quality and reusable lessons across tasks +- `goals` — Deeper goal-setting and milestone design +- `calendar-planner` — Calendar-driven planning and scheduling support +- `notes` — Structured note capture for ongoing work and thinking + +## Feedback + +- If useful: `clawhub star productivity` +- Stay updated: `clawhub sync` diff --git a/_meta.json b/_meta.json new file mode 100644 index 0000000..97552c3 --- /dev/null +++ b/_meta.json @@ -0,0 +1,6 @@ +{ + "ownerId": "kn73vp5rarc3b14rc7wjcw8f8580t5d1", + "slug": "productivity", + "version": "1.0.4", + "publishedAt": 1773250749518 +} \ No newline at end of file diff --git a/adhd.md b/adhd.md new file mode 100644 index 0000000..bae247c --- /dev/null +++ b/adhd.md @@ -0,0 +1,63 @@ +# ADHD Productivity + +The ADHD trap: standard productivity advice is written for neurotypical brains. + +--- + +## What Actually Fails + +**"Just Use a Planner"** +Planners work for brains that remember to check them. ADHD brains need external reminders, not silent notebooks. + +**"Just Focus"** +Executive dysfunction means "just focusing" is like telling someone with broken legs to "just walk." The hardware doesn't work that way. + +**Willpower-Based Systems** +Any system requiring consistent daily willpower will fail. ADHD brains have inconsistent access to motivation. + +**Long-Term Thinking** +Deadlines 2 months away don't feel real. Only the immediate triggers action. + +**Rigid Routines** +Fixed schedules bore quickly. The ADHD brain craves novelty, not repetition. + +--- + +## What Actually Works + +**External Brain** — Phone alarms, visual reminders, smart speakers, accountability partners. Get cues OUT of your head. + +**Body Doubling** — Working alongside someone (in person or virtual) provides external focus that internal systems can't. + +**Artificial Deadlines** — Create urgency: work sessions with others, scheduled accountability, public commitments. + +**Task Breakdown Extreme** — "Work on project" is too vague. "Open document" is actionable. Smaller than you think. + +**Novelty Injection** — New locations, new music, new tools. Use novelty as fuel instead of fighting it. + +**Forgive and Restart** — Missed a day? A week? It doesn't matter. Start now. Guilt is the enemy. + +**Leverage Hyperfocus** — When hyperfocus arrives, ride it. Cancel everything. These windows are gold. + +--- + +## Energy Reality + +- Interest-based attention, not importance-based +- Time blindness is real — use timers constantly +- Medication helps many — not a moral failing +- Executive function fluctuates — plan for bad days + +--- + +## Emotional Reality + +- ADHD often comes with rejection sensitivity +- Shame spirals destroy more than missed tasks +- Self-compassion is a productivity tool + +--- + +## The Real Issue + +ADHD productivity problems are neurological, not moral. The solution isn't trying harder — it's building systems that work WITH the ADHD brain, not against it. diff --git a/burnout.md b/burnout.md new file mode 100644 index 0000000..1c2e9c0 --- /dev/null +++ b/burnout.md @@ -0,0 +1,65 @@ +# Burnout Productivity + +The burnout trap: optimizing a system that's already breaking you. + +--- + +## What Actually Fails + +**More Efficiency** +Burnout doesn't need better systems. Adding productivity techniques to burnout is pouring water into a cracked container. + +**"Just Push Through"** +The mindset that created burnout cannot fix it. Harder work makes it worse. + +**Weekend Recovery** +Two days cannot undo what five days destroy. If you need weekends to survive, the weeks are the problem. + +**Vacation as Cure** +A week off doesn't fix systemic overload. You'll return to the same conditions that burned you out. + +**Toxic Positivity** +"You got this!" and "Stay positive!" dismiss the real problem. Burnout isn't an attitude issue. + +**Guilt About Resting** +"I should be productive" while resting guarantees you never actually rest. + +--- + +## What Actually Works + +**Subtraction, Not Addition** — What can you stop doing? Drop commitments, projects, responsibilities. Empty space heals. + +**Minimum Viable Everything** — Good enough is the new excellent. Save your energy for what truly matters (often: nothing right now). + +**Physical First** — Sleep, food, movement. Brain fog and exhaustion clear only after body recovers. + +**Hard Boundaries** — No email after 6pm. No weekend work. No exceptions. Negotiate explicitly if needed. + +**Small Pleasures** — What used to bring joy before burnout? Music, walks, hobbies. Not productive activities — pleasure. + +**Time to Recover** — Burnout recovery takes months, not days. Adjust expectations accordingly. + +--- + +## Warning Signs + +- Cynicism about work that used to excite you +- Exhaustion that sleep doesn't fix +- Detachment, going through motions +- Dreading Monday on Saturday morning +- Physical symptoms: headaches, insomnia, illness + +--- + +## Energy Reality + +- You have less than you think — act accordingly +- Rest feels wrong but is the only fix +- The work will survive without you (and if it won't, that's the problem) + +--- + +## The Real Issue + +Burnout is usually a systemic problem wearing individual clothes. The job demands too much, the boundaries don't exist, the culture is toxic. Productivity tips can't fix broken systems — sometimes the answer is leave. diff --git a/creative.md b/creative.md new file mode 100644 index 0000000..2c28df9 --- /dev/null +++ b/creative.md @@ -0,0 +1,53 @@ +# Creative Productivity + +The creative trap: treating inspiration like a factory output. + +--- + +## What Actually Fails + +**The Pomodoro Lie** +25-minute timers interrupt flow states. When you're finally in the zone, the timer says stop. Creative work doesn't fit neat boxes. + +**Daily Word Counts / Output Quotas** +Some days produce 3,000 words of garbage. Some days produce one perfect sentence. Measuring output ignores quality. + +**Inspiration Waiting** +"I'll write when I feel inspired" means not writing. Inspiration comes from working, not before it. + +**Forcing Morning Routines** +Many creatives work best at 11pm. The "5am creative hour" advice assumes everyone's brain peaks at the same time. + +**Treating All Work Equally** +Ideation, drafting, editing, and polishing require different energies. Forcing all in one session produces nothing good. + +--- + +## What Actually Works + +**Start in the Middle** — Don't begin at the beginning. Jump to the scene/section you're most excited about. + +**Minimum Viable Touch** — "Open the file and read yesterday's work" is enough to start. Motion creates momentum. + +**Long Sessions When Hot** — When flow arrives, cancel everything. 4-hour creative sessions are worth more than 8 half-hour sessions. + +**Separate Ideation from Execution** — Brainstorm Monday. Draft Wednesday. Edit Friday. Different modes, different days. + +**Walk Away Points** — Stop mid-sentence when you know what comes next. Tomorrow starts easy. + +**Input Matches Output** — Consuming great work feeds creating great work. Rest that includes inspiration isn't wasted time. + +--- + +## Energy Patterns + +- Creative peaks are personal — 9am or 2am, find yours +- Editing energy ≠ creating energy — don't mix +- Deadlines help some creatives, destroy others — know yourself +- Recovery is part of the process, not stealing from it + +--- + +## The Real Issue + +Creative productivity problems often mask fear: fear that the work won't be good enough, fear of finishing and being judged, fear that the well will run dry. Address the fear. diff --git a/entrepreneur.md b/entrepreneur.md new file mode 100644 index 0000000..9e9053b --- /dev/null +++ b/entrepreneur.md @@ -0,0 +1,61 @@ +# Entrepreneur Productivity + +The entrepreneur trap: wearing all hats means none fit properly. + +--- + +## What Actually Fails + +**Everything is Urgent** +When you own it all, everything feels critical. Inbox, sales, product, support, accounting — all screaming. Nothing gets deep attention. + +**Founder Martyrdom** +"I'll sleep when we're funded." "No one can do this but me." This creates burnout AND prevents building a company that works without you. + +**Shiny Object Syndrome** +New feature ideas, new markets, new partnerships — each exciting opportunity dilutes focus on what actually matters. + +**Building Before Selling** +Months perfecting product while ignoring whether anyone will pay. Building feels productive; selling feels scary. + +**Working IN the Business** +Trapped in operations, customer support, daily fires. No time for strategy, growth, or the work only you can do. + +--- + +## What Actually Works + +**One Thing Per Week** — What's the ONE thing that moves the needle? Everything else is noise. + +**CEO Day** — One day per week doing only strategic work: planning, reviewing metrics, thinking. No customer work. + +**Default Delegation** — "Who else could do this?" should be your first question, not "How do I do this?" + +**Revenue First** — Talk to customers before building. Sell before coding. Revenue validates; everything else is assumption. + +**Timeboxed Experiments** — "We'll try this for 2 weeks with $X budget." Clear boundaries prevent endless exploration. + +**Ruthless Prioritization** — The graveyard of startups is full of companies that tried to do too much. + +--- + +## Energy Reality + +- Founder energy is the company's battery — protect it +- Context switching is the default state — minimize it +- The business reflects your limits — grow yourself to grow it +- If you're always tired, the business model might be wrong + +--- + +## The Runway Reality + +- Time is the one resource you can't raise more of +- Every hour spent on low-impact work is runway burned +- "Later" often means "never" when cash runs out + +--- + +## The Real Issue + +Entrepreneur productivity problems are often prioritization problems: without external structure, everything competes equally. The skill is saying no to good things so you can focus on the right things. diff --git a/executive.md b/executive.md new file mode 100644 index 0000000..f142bd8 --- /dev/null +++ b/executive.md @@ -0,0 +1,52 @@ +# Executive Productivity + +The executive trap: your calendar is not your own, but you're still held accountable for strategic thinking. + +--- + +## What Actually Fails + +**Calendar Tetris** +Back-to-back meetings leave zero time for the thinking that justifies your role. You become a meeting attendee, not a leader. + +**The "Always Available" Spiral** +Responding instantly signals that interruptions are welcome. Soon you're managing everyone else's urgency, not your own priorities. + +**Delegation as Dumping** +Handing off tasks without context, criteria for success, or decision-making authority creates boomerang work — it comes back worse. + +**Strategy Time That Never Happens** +"I'll think about strategy this weekend" turns into firefighting because Monday brings new fires. + +**Inbox Zero Obsession** +Processing email becomes the job. Each reply generates 2 more. The inbox is infinite; your time is not. + +--- + +## What Actually Works + +**Chief of Staff Mentality** — Someone (or systems) must protect your time. If you don't have one, build the systems yourself. + +**Sacred Blocks** — 2-3 hours weekly for strategic thinking. Treat it like a board meeting. Cancel nothing for it. + +**Decision Criteria, Not Decisions** — Give your team the framework to decide. "If X, do Y. Escalate only if Z." Fewer decisions reach you. + +**First Hour = Your Hour** — Before the organization wakes up, do your most important thinking. + +**Meeting Defaults** — 25 minutes, not 30. 50 minutes, not 60. Agenda required. No agenda, no meeting. + +**Weekly 1:1 Prep** — 10 minutes before each 1:1 reviewing context. Better than winging it and missing signals. + +--- + +## Energy Reality + +- Deep thinking requires protection — it won't happen in cracks between meetings +- Decision fatigue is real — batch similar decisions, automate trivial ones +- Your energy is contagious — exhausted leader creates exhausted team + +--- + +## The Real Issue + +Executive productivity problems often mask organizational problems: unclear strategy (everything feels urgent), poor delegation systems, or wrong people in key roles. diff --git a/frameworks.md b/frameworks.md new file mode 100644 index 0000000..dc6e731 --- /dev/null +++ b/frameworks.md @@ -0,0 +1,124 @@ +# Universal Productivity Frameworks + +These apply across ALL situations. Load the relevant situation file first, then pull from here. + +--- + +## Energy Management (Not Just Time) + +Time is finite. Energy fluctuates. Match tasks to energy: + +| Energy Level | Best For | +|--------------|----------| +| High | Creative work, hard decisions, complex problems | +| Medium | Meetings, email, routine tasks | +| Low | Admin, organizing, easy mechanical work | + +Ask yourself: +- When do you feel most alert? +- When do you typically crash? +- What activities drain vs. restore you? + +--- + +## "Good Enough" Thresholds + +Perfectionism kills productivity. Define thresholds BEFORE starting: + +**A-tier tasks**: Quality matters (client deliverables, public work) +**B-tier tasks**: Just needs to work (internal docs, personal organization) +**C-tier tasks**: Done > perfect (routine emails, temporary solutions) + +Ask: "What's the minimum quality that achieves the goal?" + +--- + +## Task Initiation Protocol + +Starting is usually the only hard part. Make it trivially easy: + +1. **Identify the first physical action** + - Not "work on project" but "open file, read first paragraph" + +2. **Make it 2 minutes or less** + - Scale down until starting feels effortless + +3. **Remove friction** + - File already open, tools ready, environment set + +4. **Create a trigger** + - "After I pour my coffee, I open the document" + +--- + +## Time Blocking Essentials + +**Non-negotiable rules:** +- Blocks are appointments with yourself — treat them that way +- Buffer time between blocks (15 min minimum) +- Energy-appropriate scheduling (hard work when alert) +- Flexibility built in — one missed block doesn't break the system + +**Block types:** +- Deep work: 90-120 min, no interruptions +- Shallow work: email, messages, admin +- Buffer: transition time, overflow, unexpected +- Recovery: actual breaks, not "productive rest" + +--- + +## Boundary Scripts + +Ready-to-use phrases for protecting time: + +**For meeting requests:** +- "I have a conflict at that time. How about [alternative]?" +- "Can this be an email instead?" +- "I'm protecting that time for focused work. Here's when I'm available." + +**For interruptions:** +- "I'm in the middle of something. Can I get back to you at [time]?" +- "Let me finish this and I'll give you my full attention in 20 minutes." + +**For scope creep:** +- "Happy to add that! It's outside our original scope, so let me send a quick estimate." +- "I can do X or Y by the deadline, but not both. Which is more important?" + +**For saying no:** +- "I can't take this on right now and give it the attention it deserves." +- "That sounds interesting, but it doesn't align with my current priorities." + +--- + +## Weekly Review Template + +30 minutes, once per week: + +1. **What got done?** (Celebrate wins, even small ones) +2. **What didn't?** (No judgment — identify why) +3. **What's the ONE priority for next week?** +4. **What's blocking progress?** (Solve or escalate) +5. **What should I STOP doing?** + +--- + +## Shutdown Ritual + +Clear transition from work to not-work: + +1. Write tomorrow's top 3 priorities +2. Clear inbox to reasonable state (doesn't have to be zero) +3. Close all work tabs/apps +4. Physical signal: say "shutdown complete", close laptop, change clothes +5. Work stays at work (mentally and digitally) + +--- + +## Capture System + +Every productivity system fails without reliable capture: + +- ONE inbox (not 12 apps) +- Capture takes <30 seconds +- Review weekly (not daily — too much overhead) +- "If I don't write this down NOW, it's gone forever" mindset diff --git a/freelancer.md b/freelancer.md new file mode 100644 index 0000000..61f7275 --- /dev/null +++ b/freelancer.md @@ -0,0 +1,53 @@ +# Freelancer Productivity + +The freelancer trap: total freedom becomes total chaos. + +--- + +## What Actually Fails + +**The Pajama Problem** +No commute, no dress code, no external structure. Days blur together. "I'll start after lunch" becomes "I'll start Monday." + +**Client Availability = Your Availability** +Being always reachable feels necessary to keep clients. But it guarantees constant interruptions and no deep work. + +**Feast or Famine Work Patterns** +When busy: no time to market. When quiet: panic marketing. The cycle never stabilizes. + +**Home as Office** +Work never ends because work lives everywhere. The couch becomes stressful. The bedroom becomes anxious. No space is truly restful. + +**Isolation Spiral** +No coworkers, no water cooler, no casual feedback. The echo chamber of your own thoughts gets louder. + +--- + +## What Actually Works + +**Fake Commute** — Walk around the block to start and end work. Physical signal that the workday has boundaries. + +**Office Hours** — Tell clients: "I respond 9am-5pm." Emergencies are rare — most things can wait 4 hours. + +**Admin Day** — One day per week for invoicing, marketing, emails, planning. Protect other days for actual work. + +**Coworking (Even Occasionally)** — Coffee shop, library, or coworking space. Different environment, different energy. + +**One Client Buffer** — Always be talking to your next client before you need them. Marketing is part of the job, not something extra. + +**End-of-Day Shutdown** — Close laptop, leave office space, change clothes. Work is over. Mean it. + +--- + +## Energy Reality + +- Motivation fluctuates without external accountability +- Loneliness drains energy faster than difficult work +- Boundaries feel risky but create sustainability +- "Flexible hours" often means "all hours" + +--- + +## The Real Issue + +Freelancer productivity problems are often boundary problems: with clients, with space, with time, with yourself. Freedom without structure is chaos. diff --git a/guilt.md b/guilt.md new file mode 100644 index 0000000..8a80e8e --- /dev/null +++ b/guilt.md @@ -0,0 +1,73 @@ +# Guilt & Recovery Productivity + +The guilt trap: rest feels like failure. + +--- + +## What Actually Fails + +**Rest as Reward** +"I'll rest when I'm done" — but the to-do list never ends. Rest becomes perpetually delayed. + +**Productive Rest** +Listening to podcasts while walking, reading business books on vacation. Rest that's secretly work doesn't restore. + +**Comparison Suffering** +"They're accomplishing so much more than me" ignores invisible struggles, different circumstances, different costs. + +**Hustle Culture Internalization** +"Sleep when you're dead," "Rise and grind," "If you wanted it enough..." These slogans become the voice in your head. + +**Sunday Dread** +The weekend can't restore what the week destroys. Dreading Monday on Saturday morning is a red flag, not normal. + +--- + +## What Actually Works + +**Rest as Investment** — Rest isn't stealing from productivity; it's fueling it. Tired brains produce garbage. + +**Permission Statements** — "I am allowed to rest without earning it." "My worth is not my output." Say these out loud. + +**Actual Rest** — Naps, staring at walls, walks without podcasts. Nothing productive. Pure recovery. + +**Boundaries as Self-Care** — "No" protects your energy. Every yes to others is a no to yourself. + +**Defining Enough** — What is "enough" work for a day? Define it. Then stop when you reach it. + +**Success Reframe** — What if success meant sustainable happiness, not maximum output? + +--- + +## Hustle Damage Symptoms + +- Unable to relax without guilt +- Self-worth tied entirely to productivity +- Rest triggers anxiety +- "Lazy" feels like the worst insult +- Physical collapse required to stop + +--- + +## Recovery Phases + +1. **Permission** — Allowing yourself to rest +2. **Discomfort** — Rest feels wrong at first +3. **Practice** — Learning to relax is a skill +4. **Restoration** — Energy slowly returns +5. **Sustainable** — Rest becomes non-negotiable + +--- + +## Energy Reality + +- You cannot pour from an empty cup +- Rest is not the opposite of productivity; burnout is +- Recovery takes longer than you want +- Guilt is learned — it can be unlearned + +--- + +## The Real Issue + +Guilt-driven productivity problems are often worth problems: believing your value comes from output. The work isn't just about doing less — it's about believing you're enough without doing anything at all. diff --git a/habits.md b/habits.md new file mode 100644 index 0000000..e99d8a1 --- /dev/null +++ b/habits.md @@ -0,0 +1,72 @@ +# Habit Building Productivity + +The habit trap: starting is easy; lasting is hard. + +--- + +## What Actually Fails + +**30-Day Challenges** +Creating a finish line creates failure. Day 31, the streak breaks and the habit dies. + +**All-or-Nothing** +Miss one day = failed. This perfectionism guarantees eventual failure and shame spiral. + +**Motivation Dependence** +Starting when motivated means stopping when motivation fades. And it always fades. + +**Too Much Too Fast** +"I'll meditate 30 minutes every day" becomes zero when willpower runs out. Ambitious starts create quick failures. + +**Invisible Progress** +Without tracking, the habit feels pointless. "What's even changing?" leads to abandonment. + +--- + +## What Actually Works + +**Two-Minute Rule** — Start so small it's impossible to fail. 2 push-ups. One paragraph. 30 seconds of meditation. + +**Never Miss Twice** — Miss once, it's life. Miss twice, it's a pattern. Get back immediately. + +**Stack on Existing Habits** — "After I pour coffee, I journal." Attach new habits to established routines. + +**Identity Shift** — "I'm someone who reads" beats "I should read more." Habits follow identity, not willpower. + +**Environment Design** — Make good habits easy (book by bed), bad habits hard (phone in other room). Friction is everything. + +**Visible Streaks** — Physical calendar, app tracker, something you SEE daily. Don't track mentally. + +--- + +## The Plateau Problem + +- Excitement fades around day 14-21 +- Progress becomes invisible around day 30-60 +- The habit feels pointless around day 45 +- Knowing these are normal helps survive them + +--- + +## Energy Reality + +- Willpower depletes — design systems that don't require it +- Morning habits stick better (fewer decisions made yet) +- Stacking works because one habit triggers another +- Forgiveness is a habit too + +--- + +## Restart Protocol + +When a habit breaks: +1. No shame — it happens to everyone +2. Start today, not Monday +3. Go smaller than before +4. Ask: what made it break? Fix that. + +--- + +## The Real Issue + +Habit failures are often about environment and identity, not willpower. Change the environment, change the self-image, and habits follow. diff --git a/manager.md b/manager.md new file mode 100644 index 0000000..c5cad86 --- /dev/null +++ b/manager.md @@ -0,0 +1,59 @@ +# Manager Productivity + +The manager trap: helping everyone else succeed while your own work never happens. + +--- + +## What Actually Fails + +**Infinite Availability** +"My door is always open" = your calendar is never yours. Teams learn to interrupt instead of problem-solve. + +**Meeting Colonization** +Back-to-back 1:1s, team syncs, cross-functional alignments. No time to think, plan, or do actual work. + +**Doing Instead of Delegating** +"It's faster if I just do it" creates dependency and prevents team growth. You become the bottleneck. + +**Context-Switch Burnout** +Jumping between projects, people, and problems every 30 minutes. Mental exhaustion without tangible progress. + +**Unclear Delegation** +Handing off tasks without decision authority, success criteria, or context creates boomerang work. + +--- + +## What Actually Works + +**Office Hours, Not Open Door** — "I'm available 2-4pm for questions." Outside that: focused work time protected. + +**1:1 Prep** — 5 minutes before each 1:1 reviewing context, notes, goals. Better conversations, faster progress. + +**Decision Frameworks** — "If X, do Y. Only escalate if Z." Teams can decide without you for most things. + +**Manager Block** — 2 hours weekly for planning, strategy, documentation. Treat it like a board meeting. + +**Batch Similar Work** — All 1:1s on one day. All planning on another. Context switching kills depth. + +**Delegate Outcomes, Not Tasks** — "Make sure the report is ready by Friday" not "Write section A, then B, then..." + +--- + +## Energy Reality + +- People problems drain energy differently than task problems +- Your emotional state affects the whole team — manage it +- Saying "I need to think about this" is a complete answer +- Protecting your time models healthy behavior for your team + +--- + +## The Leverage Question + +Every hour you spend doing IC work is an hour not spent multiplying your team's output. Ask: "What can ONLY I do?" + +--- + +## The Real Issue + +Manager productivity problems are often systems problems: unclear ownership, too many meetings, insufficient delegation. Fix the system, not just your schedule. diff --git a/memory-template.md b/memory-template.md new file mode 100644 index 0000000..d98ff8c --- /dev/null +++ b/memory-template.md @@ -0,0 +1,59 @@ +# Memory Template — Productivity + +Create `~/productivity/memory.md` with this structure: + +```markdown +# Productivity Memory + +## Status +status: ongoing +version: 1.0.4 +last: YYYY-MM-DD +integration: pending + +## Constraints + + + +## Work Style + + + +## Energy Patterns + + + +## Planning Preferences + + + +## Current Friction + + + +## Review Rhythm + + + +## Notes + + +--- +*Updated: YYYY-MM-DD* +``` + +## Status Values + +| Value | Meaning | Behavior | +|-------|---------|----------| +| `ongoing` | Still learning the user's system | Gather context naturally | +| `complete` | Local system is in active use | Work from the existing files | +| `paused` | User does not want more setup questions | Stop prompting, still help | +| `never_ask` | User said stop asking about setup/memory | Never prompt again | + +## Principles + +- Store stable patterns, not every temporary mood +- Save only what helps future prioritization or planning +- Prefer constraints and preferences over life-story detail +- If it belongs in the active system, put it in `~/productivity/` files instead of memory diff --git a/migration.md b/migration.md new file mode 100644 index 0000000..9925184 --- /dev/null +++ b/migration.md @@ -0,0 +1,87 @@ +# Migration Guide - Productivity + +## v1.0.4 Productivity Operating System Update + +This update keeps the same home folder, `~/productivity/`, but changes the recommended structure from a light memory-only setup into a fuller operating system with named folders for inbox, goals, projects, tasks, habits, planning, reviews, commitments, focus, routines, and someday items. + +### Before + +- `~/productivity/memory.md` +- optional loose notes such as `~/productivity/.md` +- older installs may also have copied context guides in a flat layout + +### After + +- `~/productivity/memory.md` +- `~/productivity/inbox/` +- `~/productivity/dashboard.md` +- `~/productivity/goals/` +- `~/productivity/projects/` +- `~/productivity/tasks/` +- `~/productivity/habits/` +- `~/productivity/planning/` +- `~/productivity/reviews/` +- `~/productivity/commitments/` +- `~/productivity/focus/` +- `~/productivity/routines/` +- `~/productivity/someday/` +- any old loose notes preserved until the user chooses to merge or archive them + +## Safe Migration + +1. Check whether `~/productivity/` already exists. + +2. If it exists, keep `memory.md` exactly as it is. + +3. Create the new files without deleting the old ones: + +```bash +mkdir -p ~/productivity/{inbox,goals,projects,tasks,habits,planning,reviews,commitments,focus,routines,someday} +touch ~/productivity/inbox/capture.md +touch ~/productivity/inbox/triage.md +touch ~/productivity/dashboard.md +touch ~/productivity/goals/active.md +touch ~/productivity/goals/someday.md +touch ~/productivity/projects/active.md +touch ~/productivity/projects/waiting.md +touch ~/productivity/tasks/next-actions.md +touch ~/productivity/tasks/this-week.md +touch ~/productivity/tasks/waiting.md +touch ~/productivity/tasks/done.md +touch ~/productivity/habits/active.md +touch ~/productivity/habits/friction.md +touch ~/productivity/planning/daily.md +touch ~/productivity/planning/weekly.md +touch ~/productivity/planning/focus-blocks.md +touch ~/productivity/reviews/weekly.md +touch ~/productivity/reviews/monthly.md +touch ~/productivity/commitments/promises.md +touch ~/productivity/commitments/delegated.md +touch ~/productivity/focus/sessions.md +touch ~/productivity/focus/distractions.md +touch ~/productivity/routines/morning.md +touch ~/productivity/routines/shutdown.md +touch ~/productivity/someday/ideas.md +``` + +4. If the user has older free-form topic files in `~/productivity/`, map them gradually: + - current priorities -> `dashboard.md` + - goals -> `goals/active.md` + - projects -> `projects/active.md` + - actionable work -> `tasks/next-actions.md` + - habits and routines -> `habits/active.md` + - focus notes -> `focus/sessions.md` or `focus/distractions.md` + - weekly reset notes -> `reviews/weekly.md` + - parked ideas -> `someday/ideas.md` + +5. If older copied guide files exist in a flat layout, preserve them as legacy references. Do not delete or rename them automatically. + +6. Only clean up legacy files after the user confirms the new structure is working. + +## Post-Migration Check + +- `memory.md` still contains the user's saved preferences +- active priorities are visible in `dashboard.md` +- next actions live in `tasks/next-actions.md` +- review cadence is captured in `reviews/weekly.md` +- no legacy file was deleted without explicit user approval diff --git a/parent.md b/parent.md new file mode 100644 index 0000000..b6f841c --- /dev/null +++ b/parent.md @@ -0,0 +1,53 @@ +# Parent Productivity + +The parent trap: productivity advice assumes you control your time. You don't. + +--- + +## What Actually Fails + +**Morning Routines** +"Wake up at 5am before the kids" works until the baby wakes at 4:30. Or you're so exhausted that 5am start means 2pm crash. Or the toddler learns to wake up early too. + +**Time Block Fantasy** +2-hour deep work blocks don't exist when someone might need you any second. Planning for uninterrupted time creates frustration, not results. + +**Comparison to Pre-Kid Self** +"I used to do so much more" — yes, with 8 hours of sleep and zero dependents. That person doesn't exist anymore. Mourn them and move on. + +**"Quality Time" Guilt** +Every minute not with kids feels like stealing. Every minute with kids feels like you should be working. Both states produce guilt, zero productivity. + +**Waiting for Things to Calm Down** +There's no calm phase coming. Newborn chaos becomes toddler chaos becomes school logistics becomes teen drama. Adapt now. + +--- + +## What Actually Works + +**Micro-Sessions** — 15 minutes of focused work is real work. Stop waiting for 2-hour blocks that don't exist. + +**Nap Time is Sacred** — When they sleep, you do your ONE most important task. Not laundry. Not dishes. The one thing only you can do. + +**Lower the Bar** — "Good enough" parenting + "good enough" work beats trying to be perfect at either. + +**Tag-Team Windows** — If you have a partner, trade off. "You have 7-9pm, I have 9-11pm." Clear ownership. + +**Embrace Inefficiency** — Work will take longer with interruptions. Budget for it. Remove the surprise. + +**Visible Work** — Kids see you working, not just disappeared. They learn focus has value. + +--- + +## Energy Reality + +- Sleep deprivation changes everything — adjust expectations +- Parent guilt is exhausting — it counts as work +- You need recovery too — not optional, survival +- What worked last month won't work this month + +--- + +## The Real Issue + +Parent productivity problems are often capacity problems: you literally have less time and energy. The solution isn't better systems; it's radical prioritization and dropped expectations. diff --git a/remote.md b/remote.md new file mode 100644 index 0000000..4d68085 --- /dev/null +++ b/remote.md @@ -0,0 +1,62 @@ +# Remote Work Productivity + +The remote trap: without boundaries, work expands to fill all space. + +--- + +## What Actually Fails + +**Always Online** +Green status from 8am to 10pm signals availability, not productivity. It guarantees interruptions and prevents deep work. + +**Time Zone Martyrdom** +"I'll just take this 6am call." "I can do the 11pm sync." Soon your calendar spans 18 hours across zones. + +**No Physical Separation** +Laptop on the couch, phone by the bed, Slack on your watch. Work infects every space. No room is restful. + +**Performative Work** +Without visibility, anxiety creates busy-work: excessive messages, unnecessary updates, presence theater. + +**Isolation Default** +Days pass without speaking to humans. Loneliness accumulates. Work becomes the only social outlet (an unhealthy one). + +--- + +## What Actually Works + +**Hard Start and Stop** — 9am you start. 6pm you stop. Laptop closes. Notifications pause. Non-negotiable. + +**Physical Boundaries** — Work happens in one room/space. When you leave that space, work is over. + +**Async First** — Not everything needs a meeting. Write it down. Record a Loom. Respect time zones. + +**Communication Windows** — "I respond to Slack 10am-12pm and 3pm-5pm." Deep work happens in between. + +**Intentional Social** — Schedule calls with coworkers, join virtual coworking, work from cafés. Combat isolation actively. + +**Visible Results** — Document what you accomplish, not when you're online. Outcomes over hours. + +--- + +## Time Zone Tactics + +- Identify the 3-4 hour overlap window — protect it for sync work +- Async is the default — sync is the exception +- "Your Tuesday morning is my Monday night" — communicate time explicitly +- Not all meetings need you — empower others to decide + +--- + +## Energy Reality + +- No commute = no transition time — create one artificially +- Video calls are exhausting — use audio when possible +- Choice overload (when to work, where to work) drains energy +- Rituals replace the structure office used to provide + +--- + +## The Real Issue + +Remote productivity problems are usually boundary problems: work bleeds into life because nothing physical stops it. Build the boundaries yourself — no one else will. diff --git a/setup.md b/setup.md new file mode 100644 index 0000000..876d26d --- /dev/null +++ b/setup.md @@ -0,0 +1,114 @@ +# Setup — Productivity + +## Philosophy + +This skill should work from minute zero. + +Do not make the user complete a productivity migration project before they can get help. Answer the immediate request first, then progressively turn repeated planning work into a trusted local system. + +## On First Use + +### Priority #1: Answer the Current Productivity Problem + +If the user asks to plan, prioritize, review, or recover focus, help immediately. + +Only propose setup when it will reduce future friction. + +### Priority #2: Offer Lightweight Integration + +Ask once, naturally: + +> "Want me to set up a local productivity system so goals, projects, tasks, habits, and reviews stop living in random places?" + +If yes, create `~/productivity/` and the baseline files. + +If no, help anyway and mark integration as declined in `~/productivity/memory.md` only if the user wants memory enabled. + +### Priority #3: Tune Activation Briefly + +After wiring the default routing, ask one short follow-up: + +> "I wired this to trigger for planning, prioritization, goals, projects, tasks, habits, reviews, and overload resets. Want to also trigger it for anything else?" + +If the user names extra situations, update the routing snippet instead of inventing separate memory. + +## Local Productivity Structure + +When the user wants the system installed locally: + +```bash +mkdir -p ~/productivity/{inbox,goals,projects,tasks,habits,planning,reviews,commitments,focus,routines,someday} +``` + +Then create: +- `~/productivity/memory.md` from `memory-template.md` +- `~/productivity/inbox/capture.md` from `system-template.md` +- `~/productivity/inbox/triage.md` from `system-template.md` +- `~/productivity/dashboard.md` from `system-template.md` +- `~/productivity/goals/active.md` from `system-template.md` +- `~/productivity/goals/someday.md` from `system-template.md` +- `~/productivity/projects/active.md` from `system-template.md` +- `~/productivity/projects/waiting.md` from `system-template.md` +- `~/productivity/tasks/next-actions.md` from `system-template.md` +- `~/productivity/tasks/this-week.md` from `system-template.md` +- `~/productivity/tasks/waiting.md` from `system-template.md` +- `~/productivity/tasks/done.md` from `system-template.md` +- `~/productivity/habits/active.md` from `system-template.md` +- `~/productivity/habits/friction.md` from `system-template.md` +- `~/productivity/planning/daily.md` from `system-template.md` +- `~/productivity/planning/weekly.md` from `system-template.md` +- `~/productivity/planning/focus-blocks.md` from `system-template.md` +- `~/productivity/reviews/weekly.md` from `system-template.md` +- `~/productivity/reviews/monthly.md` from `system-template.md` +- `~/productivity/commitments/promises.md` from `system-template.md` +- `~/productivity/commitments/delegated.md` from `system-template.md` +- `~/productivity/focus/sessions.md` from `system-template.md` +- `~/productivity/focus/distractions.md` from `system-template.md` +- `~/productivity/routines/morning.md` from `system-template.md` +- `~/productivity/routines/shutdown.md` from `system-template.md` +- `~/productivity/someday/ideas.md` from `system-template.md` + +## AGENTS Routing Snippet + +If the user wants stronger routing, suggest adding this to `~/workspace/AGENTS.md` or the equivalent workspace guidance: + +```markdown +## Productivity Routing + +Use `~/productivity/` as the source of truth for goals, projects, priorities, tasks, habits, focus, planning, reviews, and overload recovery. +When the user asks to plan work, reprioritize, review commitments, reset routines, or turn goals into execution, consult the smallest relevant productivity folder first. +Prefer updating one trusted system over scattering tasks across ad-hoc notes. +``` + +## SOUL Steering Snippet + +If the user uses `SOUL.md`, suggest adding: + +```markdown +**Productivity** +When work touches priorities, commitments, planning, or review, route through `~/productivity/`. +Keep one coherent productivity system: goals in `goals/`, projects in `projects/`, execution in `tasks/`, habits in `habits/`, planning in `planning/`, focus protection in `focus/`, resets in `reviews/`, routines in `routines/`, and parked ideas in `someday/`. +Use energy, constraints, and real context before prescribing routines. +``` + +## What to Save + +Save to `~/productivity/memory.md` only with explicit approval: +- energy patterns that keep recurring +- stable planning preferences +- recurring constraints +- review cadence preferences +- system-level likes/dislikes + +## Status Values + +| Status | When to use | +|--------|-------------| +| `ongoing` | Default. Still learning how the user works. | +| `complete` | System is installed and the user actively uses it. | +| `paused` | User does not want more setup questions right now. | +| `never_ask` | User said stop prompting about setup or memory. | + +## Golden Rule + +If the skill becomes another productivity project instead of helping the user get clear and move, it failed. diff --git a/student.md b/student.md new file mode 100644 index 0000000..a648f76 --- /dev/null +++ b/student.md @@ -0,0 +1,48 @@ +# Student Productivity + +The student trap: treating education like a marathon when it's actually sprints with deadlines. + +--- + +## What Actually Fails + +**The Semester Start Fantasy** +Planning to "study every day this semester" never survives week 3. Students create elaborate schedules that assume perfect discipline — then one missed day creates cascade failure. + +**Deadline-Driven Panic** +No work happens until panic kicks in. The brain learns: "I only perform under pressure." This creates anxiety dependency and destroys any chance of steady progress. + +**The Library All-Day Trap** +12-hour library sessions feel productive but yield 2-3 hours of actual work. The rest is phone breaks, chatting, fake-studying, and exhaustion-staring. + +**Perfectionism on Wrong Tasks** +Spending 6 hours on citation formatting while the argument itself is weak. Optimizing notes organization instead of understanding the material. + +--- + +## What Actually Works + +**"Just One Pomodoro"** — Start with 25 minutes, reassess after. Starting is 90% of the battle. + +**Work Before Class** — Use the hour before class for that subject. Material is fresher, deadline closer, fewer distractions. + +**Study Groups for Accountability, Not Learning** — Groups are best for showing up, not for understanding. Deep learning happens alone. + +**Minimum Viable Progress** — "I will read ONE page" is better than "I will study for 4 hours" that never starts. + +**Weekend Morning Rule** — Get 2 hours of work done Saturday/Sunday morning. Rest of weekend is guilt-free. + +--- + +## Energy Patterns + +- Peak focus often 10am-1pm and 8pm-11pm +- Post-lunch crash is real — schedule easy tasks +- Cramming works short-term but destroys long-term retention +- Sleep deprivation makes studying worthless + +--- + +## The Real Issue + +Most student productivity problems are fear problems: fear of failure, fear of not being good enough, fear of starting and confirming you don't understand. Address the fear first. diff --git a/system-template.md b/system-template.md new file mode 100644 index 0000000..b8b26d1 --- /dev/null +++ b/system-template.md @@ -0,0 +1,292 @@ +# Productivity System Template + +Use these as the baseline files for `~/productivity/`. + +## inbox/capture.md + +```markdown +# Capture + +- Raw capture: +- Loose commitment: +- Idea to sort later: +``` + +## inbox/triage.md + +```markdown +# Inbox Triage + +- Move to goals if it is an outcome +- Move to projects if it needs coordination +- Move to tasks if it is actionable now +- Move to someday if it is not committed +``` + +## dashboard.md + +```markdown +# Productivity Dashboard + +## Current Focus +- Top priority: +- Secondary priority: +- Protect this week: + +## Active Goals +- Goal: + - Why it matters: + - Current project: + - Next milestone: + +## Active Projects +- Project: + - Owner: + - Deadline: + - Next action: + +## Risks +- What is slipping? +- What needs a decision? +``` + +## goals/active.md + +```markdown +# Active Goals + +- Goal: + - Why: + - Deadline: + - Current milestone: + - Next project: +``` + +## goals/someday.md + +```markdown +# Someday Goals + +- Goal worth revisiting: +``` + +## projects/active.md + +```markdown +# Active Projects + +- Project: + - Linked goal: + - Owner: + - Deadline: + - Next action: +``` + +## projects/waiting.md + +```markdown +# Waiting Projects + +- Project: + - Waiting on: + - Follow-up date: +``` + +## tasks/next-actions.md + +```markdown +# Next Actions + +- [ ] Concrete task +``` + +## tasks/this-week.md + +```markdown +# This Week + +- [ ] Must ship +- [ ] Important but flexible +``` + +## tasks/waiting.md + +```markdown +# Waiting For + +- [ ] Item — waiting on: +``` + +## tasks/done.md + +```markdown +# Done + +- [x] Finished item +``` + +## habits/active.md + +```markdown +# Active Habits + +- Habit: + - Trigger: + - Minimum version: + - Why it matters: +``` + +## habits/friction.md + +```markdown +# Habit Friction + +- What breaks consistency: +- What makes the habit easier: +``` + +## planning/daily.md + +```markdown +# Daily Plan + +## Must-Win +- + +## Top 3 +- + +## Protected Focus +- +``` + +## planning/weekly.md + +```markdown +# Weekly Plan + +## Outcomes +- + +## Protected Time +- + +## Constraints +- +``` + +## planning/focus-blocks.md + +```markdown +# Focus Blocks + +- Block: + - Purpose: + - Best window: + - Recovery after: +``` + +## focus/sessions.md + +```markdown +# Focus Sessions + +- Session: + - Target: + - Length: + - Result: +``` + +## focus/distractions.md + +```markdown +# Distractions + +- Trigger: + - Pattern: + - Countermeasure: +``` + +## reviews/weekly.md + +```markdown +# Weekly Review + +## Wins +- + +## What Stalled +- + +## What to Drop +- + +## Next Week Focus +- +``` + +## reviews/monthly.md + +```markdown +# Monthly Review + +## Wins +- + +## Patterns +- + +## What Changes Next Month +- +``` + +## commitments/promises.md + +```markdown +# Promises + +- Commitment: + - To: + - Deadline: + - Status: +``` + +## commitments/delegated.md + +```markdown +# Delegated + +- Item: + - Delegated to: + - Check-in date: +``` + +## routines/morning.md + +```markdown +# Morning Routine + +- First task: +- First check: +- What must not happen: +``` + +## routines/shutdown.md + +```markdown +# Shutdown Routine + +- What to close: +- What to capture: +- What becomes tomorrow's must-win: +``` + +## someday/ideas.md + +```markdown +# Someday / Ideas + +- Idea: +- Opportunity: +- Maybe later: +``` diff --git a/traps.md b/traps.md new file mode 100644 index 0000000..e746c89 --- /dev/null +++ b/traps.md @@ -0,0 +1,126 @@ +# Productivity Traps + +Things to AVOID saying or suggesting. These backfire. + +--- + +## Universal Anti-Patterns + +### Generic Advice Without Context +❌ "Just make a to-do list" +❌ "Try the Pomodoro technique" +❌ "Wake up at 5am" +❌ "Start your day with exercise" + +These aren't wrong — they're INCOMPLETE. Without understanding their situation, energy, constraints, and history, generic advice wastes their time (they've heard it) and damages trust (you don't understand them). + +**Instead**: Ask about their context first. Then adapt the advice. + +--- + +### Hustle Culture Reinforcement +❌ "Maximize every hour" +❌ "Successful people do X" +❌ "You're not reaching your potential" +❌ "Sleep when you're dead" + +For the guilt-ridden or burned-out, this is poison. It reinforces the exact mindset damaging them. + +**Instead**: Permission to rest, boundaries, sustainability framing. + +--- + +### One-Size-Fits-All Systems +❌ Assuming everyone can control their schedule +❌ Assuming everyone works 9-5 +❌ Assuming everyone has quiet space +❌ Assuming "just block time" works for parents with kids + +**Instead**: Ask about constraints. Adapt to their reality. + +--- + +### Shame or Guilt +❌ "You should be doing better" +❌ "Why haven't you tried X?" +❌ "If you really wanted it, you'd find time" +❌ Making them feel bad for missing days + +Shame doesn't motivate — it paralyzes. Especially for ADHD, burnout, and guilt personas. + +**Instead**: Neutral tone, reframes, small wins celebrated. + +--- + +### Complexity Theater +❌ Elaborate multi-app systems +❌ Daily reviews + weekly reviews + monthly reviews +❌ 12-step morning routines +❌ Anything requiring consistent daily maintenance + +Complex systems get abandoned. Simple systems survive. + +**Instead**: One tool, one ritual, minimum viable process. + +--- + +### Ignoring Emotional Reality +❌ Pure optimization advice for someone drowning +❌ Efficiency tips for someone who needs permission to rest +❌ Systems for someone whose real problem is fear + +Productivity problems are often emotional problems in disguise. + +**Instead**: Address the underlying issue. Fear, guilt, burnout, imposter syndrome. + +--- + +## Situation-Specific Traps + +### For Students +❌ Rigid schedules that break when one day is skipped +❌ "Just start" without task breakdown +❌ Assuming they'll stick to morning routines + +### For Executives +❌ Individual contributor advice +❌ Assuming they control their calendar +❌ Ignoring that others schedule their time + +### For Parents +❌ "Wake up before the kids" +❌ Advice requiring 2-hour focus blocks +❌ Judgment about shortcuts + +### For Creatives +❌ Treating creative work like assembly line work +❌ Rigid time blocks for inspiration +❌ Pomodoro for flow states + +### For ADHD +❌ "Just use a planner" +❌ "Try harder" / "Just focus" +❌ Neurotypical advice +❌ Guilt or shame + +### For Burnout +❌ More optimization (they need less, not more) +❌ "You got this!" toxic positivity +❌ Assuming rest will fix systemic problems + +### For Habit Building +❌ 30-day challenges (creates finish line) +❌ Waiting for them to report progress +❌ All-or-nothing framing + +--- + +## The Meta-Trap + +The biggest trap: Giving productivity advice to someone who actually needs: +- Permission to rest (guilt persona) +- Medical support (burnout, ADHD) +- Systemic change (toxic workplace) +- Emotional processing (fear, trauma) + +**Always check**: Is productivity the real problem, or a symptom?