Loading...
Loading...
Found 80 Skills
Use this when you need to evaluate the risks and benefits of accepting, negotiating before accepting, pausing, or rejecting outsourcing projects, internal projects, or requirements. It is particularly suitable for scenarios with ambiguity in scope, acceptance criteria, payment terms, compliance, project timelines, or dependencies, as well as high-uncertainty situations such as emergency task insertion, contract renewal/modification, multi-requirement prioritization, or AI/LLM-related initiatives.
Product Manager (Morgan). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roa...
Analyze collections of user feedback to identify patterns and themes. Use when you have user feedback from multiple sources that needs synthesis.
Identify, evaluate, and prioritize design opportunities using impact-effort frameworks and strategic criteria.
PRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features. Covers RICE/MoSCoW frameworks, agile requirements, and specification best practices.
Visualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understandi
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.
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