Total 50,523 skills, Project Management has 1846 skills
Showing 12 of 1846 skills
Generate an ethos/ folder that captures a project's vision, principles, personas, and non-goals — the 50k-foot "why behind the what." Use when the user wants to establish project philosophy, define guiding principles, document who the product is for, or create foundational context that agents and humans can reference for decision-making. Triggers: "create an ethos", "define project principles", "document our vision", "set up project philosophy", "who is this product for."
Pick and work on the next task from TASKS.md. Use when the user says "next task", "work on the next thing", "what should I work on", or wants to start an autonomous coding loop.
Workflow for handling a Linear issue end-to-end. Uupdate Linear, create a git worktree from dev, implement the change, verify it, and open a GitHub PR linked to the issue.
This skill should be used when the user asks to "create a blueprint", "blueprint this feature", "plan this implementation", "make a plan", "create an implementation plan", "design the architecture", "design this feature", or "break this down into steps".
This skill should be used when the user has a written implementation plan to execute in a separate session with review checkpoints.
Create a detailed execution plan for implementing features or refactors in a codebase by leveraging existing research in the specified `research` directory.
Trigger: Invoked when multiple tasks are competing for time, attention, computing power or budget at the same time, and it is necessary to determine the main attack direction and stop dispersing efforts; common signals include too many priorities, tight resources, scattered progress, and the need to decide what to do first. English: Trigger when limited resources are being split across too many tasks and one main target must be chosen. Use this skill to concentrate effort, sequence work decisively, and finish a meaningful breakthrough before expanding.
Trigger: Invoke when you start from scratch with extremely limited resources and need to find the minimum viable entry point first to build a stable base. Common signals include bootstrap, MVP, pilot, first foothold, and small team startup. Trigger when starting from almost nothing and needing a viable foothold before scaling up. Use this skill to build a durable base, start small, and grow from a validated nucleus instead of scattering effort.
Create context handoff when pausing work mid-phase
Apply systems thinking — causal loop diagrams, stock-and-flow models, system archetypes, and leverage-point analysis — to organizational, economic, or social problems where feedback loops, delays, or emergent behavior drive recurring failure across multiple interacting actors. Use this skill when the user describes a multi-actor situation that resists linear fixes: policy interventions that backfire, org-level fixes that break other teams, market symptoms that return after being solved, or time-lagged second-order consequences, even if they say 'why does fixing X make Y worse' or 'identify the leverage points in this system'. Do NOT use for single-cause software bugs, flaky tests, or regressions — those are debugging problems, not systems-thinking problems, even when phrased as 'this keeps coming back'.
Apply the Balanced Scorecard (BSC) framework to translate strategy into measurable objectives across Financial, Customer, Internal Process, and Learning & Growth perspectives. Use this skill when the user needs to set strategic KPIs, create a strategy map, align organizational goals, or connect daily operations to strategic vision — even if they say 'how do we measure strategy execution' or 'our KPIs feel disconnected'.
Identify and analyze cognitive biases including confirmation bias, anchoring, availability heuristic, and sunk cost fallacy in decision-making contexts. Use this skill when the user needs to audit a decision for bias, understand why a team keeps making the same mistakes, design debiasing interventions, or evaluate whether a conclusion is based on evidence or cognitive shortcuts — even if they say 'are we fooling ourselves', 'why do we keep getting this wrong', or 'is this analysis biased'.