Discover tools project management skills, compare source repositories and read the instructions for each workflow.
A three-part structural framework for building a scalable company—Foundation (Founding Documents), Posts & Beams (Supporting Structures), and Mechanicals (Operating Cadence). Use when moving from PMF to scaling...
Use when running experiments on platforms where user value compounds over time, when growth teams claim credit for revenue that would have happened anyway, or when short-term wins don't translate to long-term v...
A leadership cadence where the CEO/Leader reviews actual work (designs, prototypes, copy) weekly rather than just metrics or status slides. Use when feeling product quality is slipping or team is moving too slo...
A goal-setting mental model where leaders increase the target by 10x to force teams to abandon current processes and use first-principles thinking. Use during annual planning when teams default to safe, increme...
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
Diagnose team problems by checking structural issues (goals/roles) at the surface before diving deep into personality conflicts. 80% of team problems are structural, not personal.
Learn how to create effective project skills following opence conventions.
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
MUST use when interacting with Shortcut's project management platform to create, update, search, or retrieve stories, epics, iterations, teams, workflows, objectives, and documents.
MUST use when interacting with Shortcut's project management platform to create, update, search, or retrieve stories, epics, iterations, teams, workflows, objectives, and documents.
SUB-AGENT ONLY: This skill should be used when spawned for read-only research - generates report file and outputs [AGENT_DONE] marker.
This skill should be used at conversation start when user mentions parallel, multiple tasks/features, worktrees, lists 2+ independent work items, or similar keywords - determines which polydev skill to use.
This skill should be used when creating detailed implementation plans for polydev parallel tasks - generates step-by-step PLAN.md files.
Onboard new projects with standardized configuration and documentation
Design and implement n8n workflow automations with best practices
Import markdown documents and mermaid diagrams into Joplin using the Joplin CLI.
Podcast production patterns and workflows. Use when recording podcasts, editing audio, transcribing episodes, generating show notes, RSS feed management, or podcast distribution.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures u...
Navigate and understand Octopus structure across spaces, environments, and projects
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and crea...
Use when asked to "run a design sprint", "5-day sprint", "prototype in a week", "test ideas before building", or "Jake Knapp sprint". Helps teams go from problem to tested prototype in five days. The Design Spr...
Use when asked to "opportunity solution tree", "OST", "Teresa Torres", "map customer opportunities to outcomes", "structure discovery around opportunities", or "compare solutions for a customer need". Helps pro...
Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scru...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.