deep-productivity

hexbee/hello-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/hexbee/hello-skills --skill deep-productivity
0 commentsdiscussion
summary

Master deep work with a three-part framework: 1 hour daily of Building, balanced with Maintenance and Recovery.

  • Establish sustainable productivity through a 90-day transformation sequence: diagnose focus state, define vision and anti-vision, build a 10-year-to-daily goal hierarchy, and apply project-based learning to close skill gaps
  • Identify lever-moving tasks that actually progress goals using the challenge-equals-skill principle, avoiding both anxiety (challenge too high) and boredom
skill.md

Deep Productivity Mastery

Transform your life with just 1 hour/day of focused building work. This skill applies the three types of work framework—Building, Maintenance, and Recovery—to help you create meaningful progress toward your goals.

When to Use This Skill

  • User wants to build something meaningful (business, creative work, personal project)
  • User struggles with focus, distractions, or unclear priorities
  • User has limited time (1 hour/day) and wants to maximize impact
  • User feels stuck in "doing mode" without real progress
  • User wants to design a sustainable productivity system

Core Framework: Three Types of Work

Before diving into workflows, understand the three types of work:

  1. Building - Intense bursts of deep work to bring a project to life (products, services, brands, skills)
  2. Maintenance - Consistent, often repetitive work to keep what you built alive (marketing, customer service, operations)
  3. Recovery - Rest, leisure, and lack of narrow focused stress that allows breakthrough ideas to form

Your goal: Build for 1 hour/day until you can pursue your vision full-time. Then transition to maintenance work.

Workflow: The 90-Day Deep Work Transformation

Follow this sequence to establish a sustainable deep work practice:

Step 1: Diagnose Your Current State

Assess where you are on the focus spectrum:

State Symptoms Root Cause
Distracted Multiple programs running, attention split Lack of clarity
Anxious Overwhelmed by goals, paralyzed Challenge >> Skill
Bored Repetitive work, self-centered thoughts Challenge << Skill
Flow Challenge ≈ Skill, time flies Optimal state

Key insight: Humans can process ~50 bits of conscious info/second. Every distraction reduces your potential. You have ~125 billion bits total in a lifetime—use them wisely.

Step 2: Create Vision & Anti-Vision

Vision: Your ideal future (be specific, even if it seems irrational) Anti-Vision: What you don't want, where you'll end up without change

Exercise (15 minutes):

  1. Write out everything you DON'T want in your life—feel the discomfort
  2. Write out your ideal future—be petty, think big, ignore "rational" limits
  3. List all distractions standing between you and that future
  4. Identify people, apps, activities to temporarily remove

Rule: Success is less about discipline and more about removing distractions that make discipline difficult.

Step 3: Build Your Goal Hierarchy

Create a clear mental frame you can tap into anytime:

10-Year Goal → Where you want to be
1-Year Goal → Milestone to reach this year
1-Month Goal → What you must achieve this month
1-Week Goal → Actionable tasks this week
Lever-Moving Tasks → Daily 1-3 priorities that move the needle

Example:

  • 10-Year: Build a global digital education company
  • 1-Year: Launch MVP and get 1000 paid subscribers
  • 1-Month: Create minimum viable course product
  • 1-Week: Record 3 video lessons, set up payment system
  • Daily: Record 1 lesson (30 min), promote on social (30 min)

Step 4: Apply Project-Based Learning

Principle: Learn by building, not by consuming tutorials.

Why tutorials fail: Endless consumption creates endless options and overwhelm. Most information goes to waste because you can't apply it.

How to use project-based learning:

  1. Choose something to build that moves the needle toward your vision
  2. Brain dump everything you know about it
  3. Save 3-5 sources to emulate—study their structure
  4. Outline into sections, milestones, knowledge gaps
  5. Start building with what you know
  6. Let the project expose gaps—search for answers as needed

A project can be anything: Your health, a business, a skill, a creative work. A project is simply a structured way to achieve a goal.

Step 5: Design Your 1-Hour Deep Work Protocol

Structure your daily deep work block using the clarity-importance-urgency framework:

Before the session (2 min):

  • Review today's lever-moving task (from hierarchy)
  • Ask: "If I could only do one thing today, what would it be?"

During the session (50 min):

  • Single-task on that one thing
  • If blocked, break into smaller sub-goals
  • Apply challenge ≈ skill: if anxious, simplify; if bored, increase challenge

After the session (8 min):

  • Journal what you accomplished
  • Identify the next micro-step
  • Note any ideas that emerged ( Default Mode Network will generate insights during rest)

Optimal timing: Morning, after filling your mind with education/ideas, before emptying with planning.

Step 6: Balance Work with Recovery

Critical: Your best ideas come during rest, not during work.

Daily structure (the routine of successful creatives):

  • Morning: Creation, output, focus (deep work block)
  • Afternoon: Learning, ideas, socialization (fill your mind)
  • Evening: Journaling, planning, meditation (empty your mind)

Recovery activities (not escapism):

  • Walking (especially without phone)
  • Reading fiction or philosophy
  • Daydreaming, imagining futures
  • Meaningful conversation
  • Solitude without distractions

The Default Mode Network: When you stop focusing externally, your brain connects regions for visual thinking and creativity. This is where breakthrough ideas emerge.

Decision Tree: What to Work On

What stage are you in?
├─ Pre-foundation (no clear vision)
│  └─ Focus: Vision & Anti-Vision exercise (Step 2)
├─ Foundation (vision set, no project)
│  └─ Focus: Goal hierarchy + First project definition (Steps 3-4)
├─ Building (active project in progress)
│  └─ Focus: Daily 1-hour protocol + Lever-moving tasks (Steps 5)
└─ Maintenance (project generating value)
    └─ Focus: Systematizing, delegating, starting next project

Quick Reference: The Deep Work Checklist

Before starting each session, confirm:

  • I know exactly what one task I'm working on
  • The challenge is just above my current skill level
  • I understand WHY this matters to my future
  • Distractions are removed (phone, tabs, notifications)
  • I have a hard stop time (60 or 90 minutes max)

After each session, confirm:

  • I made measurable progress on my project
  • I identified the next micro-step
  • I captured any ideas that emerged
  • I'm transitioning to recovery (not maintenance work)

Embracing Uncertainty

Expect to feel lost, overwhelmed, and like you don't know what you're doing. This is normal and signals growth.

  • Uncertainty is signal, not noise
  • Your brain filters reality based on what you're obsessed with
  • Invest in your portfolio of failures until you can afford to succeed
  • The "certain" life is the least rewarding

Key insight: Neurons that fire together, wire together. Being extreme about your goals accelerates neuroplasticity.

Resources

references/

  • focus-types.md - Detailed breakdown of Building, Maintenance, Recovery
  • flow-formula.md - The challenge ≈ skill equation explained
  • default-mode-network.md - How recovery generates creative insights

scripts/

  • assess_focus.py - Diagnose current focus state
  • generate_hierarchy.py - Create goal hierarchy from vision statement
  • track_levers.py - Track lever-moving tasks and progress
how to use deep-productivity

How to use deep-productivity on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add deep-productivity
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/hexbee/hello-skills --skill deep-productivity

The skills CLI fetches deep-productivity from GitHub repository hexbee/hello-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/deep-productivity

Reload or restart Cursor to activate deep-productivity. Access the skill through slash commands (e.g., /deep-productivity) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.545 reviews
  • Xiao Robinson· Dec 28, 2024

    Registry listing for deep-productivity matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Luis Bansal· Dec 28, 2024

    I recommend deep-productivity for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Ganesh Mohane· Dec 20, 2024

    deep-productivity reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Xiao Martinez· Dec 8, 2024

    Useful defaults in deep-productivity — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yash Thakker· Nov 19, 2024

    We added deep-productivity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Nia Mensah· Nov 19, 2024

    Useful defaults in deep-productivity — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Michael Patel· Nov 19, 2024

    deep-productivity reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sakshi Patil· Nov 11, 2024

    I recommend deep-productivity for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Valentina Sethi· Nov 7, 2024

    We added deep-productivity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Valentina Taylor· Oct 26, 2024

    deep-productivity fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 45

1 / 5