moscow-prioritization SKILL.md skillA
moscow-prioritization from pantheon-org/tekhne is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pantheon-org/tekhne/moscow-prioritization@git:20261021.d128b5fPins git:20261021.d128b5f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pantheon-org/tekhne
- Path
skills/project-mgmt/issue-tracker-toolkit/moscow-prioritization/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261021.d128b5f, committed Oct 21, 2026
- First version recorded
- Apr 27, 2026
- Size
- 3,789 bytes
- Repository stars
- 10
- License
- MIT
MoSCoW prioritization: categorize requirements into Must Should Could Won't tiers using failure-focused test. Apply for backlog refinement, feature prioritization, sprint planning, release scope decisions, rebalance Must tier, create Won't items with revisit dates, adjudicate stakeholder disagreements, produce decision log. Keywords: prioritization, backlog, refinement, sprint planning, release scope, rebalance, stakeholder, decisions, MVP, scope control.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# MoSCoW Prioritization ## When to Use Use this skill when you need to rank requirements for a release. ## When Not to Use Do not use this skill for task-level estimation, bug triage, or sprint capacity planning by itself. ## Principles 1. `Must` means release failure if missing. 2. `Should` means high value but deferrable. 3. `Could` means optional enhancement. 4. `Won't` means explicitly out of scope for this release. ## Deterministic Workflow 1. Collect candidate requirements in one list. 2. Confirm release constraints (date, budget, team). 3. Categorize each item with the decision tree in `references/categorization-decision-tree.md`. 4. Challenge every `Must` using failure-focused questions. 5. **Validate:** Verify that the `Must` count does not exceed 60% of total effort before proceeding. 6. Rebalance if `Must` work exceeds 60% of effort. If rebalancing cannot bring `Must` under 60%, escalate to stakeholders to either re-scope the release (split into two releases, extend the timeline, or increase capacity) before finalizing categories. 7. Publish final table with owners and review date. ## Quick Commands ### Create a workshop draft ```bash …
Read the whole file at its exact version.
How to install
mdr add pantheon-org/tekhne/moscow-prioritization@sha256:5593c14003476c2aThe line at the top of this page pins the label git:20261021.d128b5f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_r7sqnzvhx56pv7dj)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 27, 2026 and Oct 21, 2026, about one every 88 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.d128b5f latest | 2026-10-21 | d128b5f | 3,789 B | A | view · diff |
| git:20261004.cc33b37 | 2026-10-04 | cc33b37 | 3,825 B | A | view · diff |
| git:20260427.dfbd28f | 2026-04-27 | dfbd28f | 3,853 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3789 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pantheon-org/tekhne · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r7sqnzvhx56pv7dj GET https://markdownregistry.com/api/v1/resolve?ref=pantheon-org/tekhne/moscow-prioritization GET https://markdownregistry.com/api/v1/blob/5593c14003476c2acc7509c2ddde8f5d834ae7d13cac731ac21a288c82ca33a4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.