Loading...
Loading...
Found 184 Skills
Defines ROI-based coverage targets with critical path identification, layer-specific targets, and explicit "don't test this" guidelines. Use for "test coverage", "coverage strategy", "test priorities", or "coverage targets".
Analyzes test coverage reports, identifies gaps, and recommends priority areas for testing. Use when reviewing coverage, finding untested code, or planning test improvements.
Plan and scope a Minimum Viable Product for a solopreneur. Use when deciding what to build first, what to cut, how to prioritize features, how to define "done" for a first launch, and how to structure the MVP build process. Covers the MVP definition, feature ruthless-cutting framework, build-vs-buy decisions, launch criteria, and post-launch learning loops. Trigger on "plan my MVP", "minimum viable product", "what should I build first", "scope my product", "MVP roadmap", "what features to include", "first version", "launch something".
Minimalist project roadmap management using a position-based priority system in ROADMAP.md. Use when users want to: (1) Create or initialize a project roadmap, (2) Add tasks/features to a roadmap, (3) Update task priorities or status, (4) Reorganize roadmap items, (5) Move tasks between sections (Inbox/Doing/Next Up/Backlog/Done), (6) Clean up or review the roadmap, or any other roadmap planning and tracking activities. Triggered by keywords like 'roadmap', 'task planning', 'project planning', 'milestone', 'priority'.
Use when research direction needs assessment, critical knowledge gaps must be identified, or priorities must be recommended based on impact, dependencies, and effort (especially at project milestones or when scope questions arise)
Enforces a 'Document-then-Execute' workflow. Use when an agent needs to run shell commands, execute tests, build projects, or perform any task that should favor established task runners (Makefile, npm run) and be logged to .cmds-by-agents/ for auditability.
This skill should be used when the user asks to "create issues from a scan", "prioritize what to fix", "rank the issues", "build a roadmap from scan results", "run Morphiq Rank", or mentions creating a prioritized roadmap from scan results. Consumes a Morphiq Scan Report, applies issue creation criteria with impact/effort weighting, and organizes issues into 4 progressive discovery tiers.
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'.
Prioritize sprint and backlog work with explicit tradeoffs. USE when choosing what fits next, sequencing backlog items, or balancing value, effort, and risk.
Plan portfolio priorities, resource bets, and strategic tradeoffs. USE when choosing where the organization should invest across multiple projects or initiatives.
Elicits and prioritises user needs (needs, pains, desires) as job stories — produces opportunities ready for product strategy
Connects user opportunities to business outcomes and solution bets — produces a strategy tree and prioritised experiments