SKILLEMALL.ai
GitHub ↗ RU Sign in

BF product-roadmapping-and-portfolio

Build and maintain outcome-based product roadmaps and portfolio views that sequence strategic bets by evidence, not dates. Covers Now/Next/Later views, strategic-bet management, capacity allocation, dependency and confidence mapping, scenario planning, continue/pause/kill/revisit criteria, stakeholder narratives, and roadmap review cadences. Use when building or reviewing a product roadmap, managing a portfolio of bets, or communicating strategic sequencing to stakeholders. Do NOT use for tactical prioritization mechanics (RICE, MoSCoW, Kano, OST — route to product-methodology or product-strategy), for project scheduling or Gantt charts, or for delivery-flow management (route to kanban-guru).

magnus919/agent-skills Agent Skills author: magnus919 MIT 12 files body ≈ 1 689 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Build and maintain outcome-based product roadmaps and portfolio views that sequence strategic bets by evidence, not dates.

As a process F 36/100 · Will not run — References files that are not bundled: ../product-methodology/SKILL.md, ../product-strategy/SKILL.md, ../strategy-frameworks/SKILL.md

GeneratorOperations and projectstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
F
36/100
Will not run
References files that are not bundled: ../product-methodology/SKILL.md, ../product-strategy/SKILL.md, ../strategy-frameworks/SKILL.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../product-methodology/SKILL.md
  • warning missing-ref reference to a missing file: ../product-strategy/SKILL.md
  • warning missing-ref reference to a missing file: ../strategy-frameworks/SKILL.md
  • warning missing-ref reference to a missing file: ../kanban-guru/SKILL.md
  • warning missing-ref reference to a missing file: ../technical-program-management/SKILL.md
  • warning missing-ref reference to a missing file: ../technical-project-management/SKILL.md
  • warning missing-ref reference to a missing file: ../implementation-planning/SKILL.md

Process rating: all ten parameters 36/100

Will not run. References files that are not bundled: ../product-methodology/SKILL.md, ../product-strategy/SKILL.md, ../strategy-frameworks/SKILL.md
  • 0Tools and files. 7 referenced file(s) missing: ../product-methodology/SKILL.md, ../product-strategy/SKILL.md, ../strategy-frameworks/SKILL.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 8 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 100Steps. 10 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1689 tokens
  • medium 6 test cases, all positive: not one "should refuse" or "should ask first"
  • low No test case covers injection arriving through data

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 701: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 10 items
  • +4Reference files are cited in the instructions (6 of 6)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.