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:
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.