CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/moscow-prioritization

Prioritize product requirements with the MoSCoW framework in a deterministic way. Use when teams need to define MVP scope, sequence releases, resolve stakeholder conflicts, prevent scope creep, or rebalance backlog under time, budget, or staffing constraints. Keywords: moscow, must should could wont, requirement prioritization, backlog, mvp, release planning, scope control, stakeholder alignment.

Overall
score

99%

Review — 99%

Does it follow best practices?

Validation — 10 / 11 Passed

Validation for skill structure

Overview
Skills
Evals
Files

effort-balancing-and-tradeoffs.mdreferences/

Effort Balancing and Tradeoffs

Use this guide after initial categorization.

Target Distribution

  • Must: 50-60% effort
  • Should: 20-30% effort
  • Could: 10-20% effort
  • Won't: explicit exclusions

Rebalance Rules

  1. If Must > 60%, downgrade lowest-impact Must items.
  2. If Could is empty, force explicit enhancement candidates.
  3. If Won't is empty, add at least 3 deferred items.

Tradeoff Examples

  • Move advanced analytics from Must to Should to protect launch date.
  • Move custom theming from Should to Could when staffing drops.
  • Move legacy export format from Could to Won't when demand is low.

Verification

Review the final mix with stakeholders and capture sign-off date.

Install with Tessl CLI

npx tessl i pantheon-ai/moscow-prioritization@0.1.0

references

categorization-decision-tree.md

effort-balancing-and-tradeoffs.md

facilitator-workshop-template.md

SKILL.md

tile.json