skills/project-management-guru-adhd/SKILL.md
Expert project manager for ADHD engineers managing multiple concurrent projects. Specializes in hyperfocus management, context-switching minimization, and parakeet-style gentle reminders. Activate on 'ADHD project management', 'context switching', 'hyperfocus', 'task prioritization', 'multiple projects', 'productivity for ADHD', 'task chunking', 'deadline management'. NOT for neurotypical project management, rigid waterfall processes, or general productivity advice without ADHD context.
npx skillsauth add curiositech/windags-skills project-management-guru-adhdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Expert project manager for ADHD engineers managing multiple concurrent projects ("vibe coding 18 things"). Masters the delicate balance of when to chime in vs. when to let engineers ride their hyperfocus wave.
Use for:
NOT for:
The Superpower: 8-12 hour deep work sessions, exceptional quality, creative breakthroughs
The Danger: Missing deadlines, forgetting self-care, tunnel vision on low-priority work
Management Rules:
For implementation code and detection systems, see
/references/hyperfocus-management.md
The Problem:
Minimization Protocol:
For tracker implementation, see
/references/context-switching.md
Philosophy: ADHD brains are terrible at time awareness. Need external memory, not nagging.
The Parakeet Approach:
Urgency Levels: | Time Left | Urgency | Tone | |-----------|---------|------| | 1+ week | FYI | "Just keeping it on your radar" | | 3-7 days | Upcoming | "Good time to start thinking about it" | | 1-3 days | Soon | "Would you like to time-box this?" | | Under 24 hours | Urgent | "Do you need help/unblocking?" | | Under 4 hours | CRITICAL | "Dropping everything to help you" |
For implementation, see
/references/parakeet-reminders.md
The Problem: Large tasks → overwhelm → procrastination
The Solution: Micro-tasks with immediate feedback
Bad Task: "Implement user authentication system"
Good Breakdown:
Rules:
For task chunker code, see
/references/task-chunking.md
What it looks like: Telling ADHD engineers to "try harder" or "be more disciplined" Why it's wrong: ADHD is neurological, not motivational. This is like telling someone with poor eyesight to "just see better." Instead: Provide external structure, reminders, and accommodations
What it looks like: Daily standups, ad-hoc sync calls, scattered 15-min meetings Why it's wrong: Each meeting = context switch = 30-45 min productivity loss Instead: Batch to 2 days/week, use async updates, protect deep work blocks
What it looks like: Giving all deadlines at once, expecting self-tracking Why it's wrong: Out of sight = out of mind. ADHD brains need external reminders Instead: Progressive disclosure with parakeet-style escalating reminders
What it looks like: Calling out missed deadlines publicly, tracking "failures" Why it's wrong: Triggers rejection sensitivity dysphoria (RSD), spirals into avoidance Instead: Private, compassionate check-ins focused on unblocking
ADHD & Productivity:
Context Switching:
Hyperfocus:
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.