Master deep work with a three-part framework: 1 hour daily of Building, balanced with Maintenance and Recovery.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondeep-productivityExecute the skills CLI command in your project's root directory to begin installation:
Fetches deep-productivity from hexbee/hello-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate deep-productivity. Access via /deep-productivity in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
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.
Before diving into workflows, understand the three types of work:
Your goal: Build for 1 hour/day until you can pursue your vision full-time. Then transition to maintenance work.
Follow this sequence to establish a sustainable deep work practice:
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.
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):
Rule: Success is less about discipline and more about removing distractions that make discipline difficult.
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:
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:
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.
Structure your daily deep work block using the clarity-importance-urgency framework:
Before the session (2 min):
During the session (50 min):
After the session (8 min):
Optimal timing: Morning, after filling your mind with education/ideas, before emptying with planning.
Critical: Your best ideas come during rest, not during work.
Daily structure (the routine of successful creatives):
Recovery activities (not escapism):
The Default Mode Network: When you stop focusing externally, your brain connects regions for visual thinking and creativity. This is where breakthrough ideas emerge.
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
Before starting each session, confirm:
After each session, confirm:
Expect to feel lost, overwhelmed, and like you don't know what you're doing. This is normal and signals growth.
Key insight: Neurons that fire together, wire together. Being extreme about your goals accelerates neuroplasticity.
focus-types.md - Detailed breakdown of Building, Maintenance, Recoveryflow-formula.md - The challenge ≈ skill equation explaineddefault-mode-network.md - How recovery generates creative insightsassess_focus.py - Diagnose current focus stategenerate_hierarchy.py - Create goal hierarchy from vision statementtrack_levers.py - Track lever-moving tasks and progressMake data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for deep-productivity matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend deep-productivity for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
deep-productivity reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in deep-productivity — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added deep-productivity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in deep-productivity — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
deep-productivity reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend deep-productivity for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added deep-productivity from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
deep-productivity fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 45