Loading...
Loading...
Found 209 Skills
Product manager that decomposes requirements into actionable tasks with priorities and dependencies
6 buying signals ranked by purchase correlation - Former Customers, New Leadership, High-Intent Website, Tech Stack Change, Expansion, and Hiring/Downsizing. Use when prioritizing outreach, building signal-based campaigns, or setting up intent tracking.
Analyze JIRA tickets to determine priority and dependency order. Outputs an ordered JIRA ID list. Use before implement/forge, or when asked to "prioritize tickets", "order these JIRAs", "what should I work on first".
Based on the KISS (Keep It Simple, Stupid) and "Minimum Viable Brilliance" complexity control principles. It is used for design and implementation decisions at all levels of projects, systems, modules, code, and functions, helping to prioritize core values, reduce unnecessary complexity, and avoid over-design. Keywords: KISS, simplification, focus, complexity control, Minimum Viable Brilliance.
Captures, enriches, tags, and prioritizes roadmap tasks. Use when the user wants to note work quickly, add missing task details, organize a backlog, or reprioritize an existing list of tasks.
Track, categorize, and prioritize technical debt when the user asks to manage tech debt, create a tech debt register, assess code quality, or plan refactoring work
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.
Vendor-neutral skill to analyze onboarding funnel dropoff and propose prioritized interventions.
Use when user asks to "discover tasks", "find next task", or "prioritize issues". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources.
Copilot agent that assists with requirements analysis, user story creation, specification definition, and acceptance criteria definition Trigger terms: requirements, EARS format, user stories, functional requirements, non-functional requirements, SRS, requirement analysis, specification, acceptance criteria, requirement validation Use when: User requests involve requirements analyst tasks.
Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions
Apply Stakeholder Theory (Freeman, 1984) and the Mitchell et al. (1997) salience model to identify, classify, and prioritize stakeholders based on power, legitimacy, and urgency. Use this skill when the user needs to map stakeholders for a project or strategy, determine which stakeholders demand immediate attention, balance competing stakeholder interests, or when they ask 'who are our key stakeholders', 'how do we prioritize conflicting demands', or 'which stakeholders can block this initiative'.