Agent skill

Moscow

by neurofoo in neurofoo/agent-skills

MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have.

MITAuto-check passedProduct & Project Management

Install Moscow

skills CLI
$ npx skills add neurofoo/agent-skills --skill moscow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install neurofoo/agent-skills moscow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/moscow .claude/skills/moscow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
moscow
GitHub stars
119
Token cost
~541 tokens
SKILL.md length
264 words
Files
3 (incl. references)
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have.

  • Scope definition
  • SKILL.md covers Instructions and Guidelines
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Feature prioritization

What it does

Moscow is an agent skill from neurofoo/agent-skills. MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have. Use for scope definition, feature prioritization, or when everything feels equally important.

Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `commands/moscow.md` and `references/examples.md`).

It sits in Product & Project Management, covering Prioritization frameworks. The repository describes itself as: Agent Skills for Claude Code and OpenCode. The licence is MIT.

When your agent uses it

  • Scope definition
  • Feature prioritization
  • Everything feels equally important

Example prompts

  • “/moscow”

What it can do on your machine

Read from SKILL.md and the folder at commit 0e7ac2a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Moscow loads about 541 tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 49 tokens; SKILL.md has 264 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~541
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from neurofoo/agent-skills at commit 0e7ac2a, republished under its MIT licence (© neurofoo). 264 words, ~541 tokens.

Download SKILL.mdSave it as .claude/skills/moscow/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
moscow
description
MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have. Use for scope definition, feature prioritization, or when everything feels equally important.
user-invocable
true

MoSCoW Prioritization

Categorize items into Must have, Should have, Could have, and Won't have for clear scope and priorities.

Instructions

Take the list of items provided and sort them into MoSCoW categories. Be rigorous about what's truly a "Must"—if the project/goal can still succeed without it, it's not a Must.

Output Format

Context What are we prioritizing for? What are the constraints (time, budget, capacity)?

Prioritized List

Must Have (Critical)

Without these, the project fails or is pointless

  • [Item] — [Why it's a must]
  • [Item] — [Why it's a must]
Should Have (Important)

Significantly adds value; painful to omit but project survives

  • [Item] — [Value it adds]
  • [Item] — [Value it adds]
Could Have (Nice to Have)

Desirable if time permits; low impact if cut

  • [Item] — [Why it's optional]
  • [Item] — [Why it's optional]
Won't Have (Not This Time)

Explicitly out of scope; may revisit later

  • [Item] — [Why it's deferred]
  • [Item] — [Why it's deferred]

Effort Distribution

CategoryItemsEst. Effort %
MustX≤60%
ShouldX~20%
CouldX~10%
Won'tX0% (deferred)

Red Flags

  • If Must > 60% of effort: scope may be too large
  • If no Won'ts: probably not being honest about constraints
  • If everything is Must: priorities haven't been set

Rationale Explain the key trade-offs made and the reasoning behind contentious categorizations.

Next Step What's the first Must item to tackle?

Guidelines

  • Ask "If we shipped without this, would we fail?" for each Must
  • Challenge "Musts" that are really "someone really wants this"
  • Make Won'ts explicit—avoids scope creep later
  • Consider dependencies (a Must might require a "hidden" Must)
  • Stakeholder alignment is essential—this isn't just your opinion

$ARGUMENTS

© neurofoo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in moscow of neurofoo/agent-skills.

  • SKILL.md
  • commands/moscow.md
  • references/examples.md

Open the folder on GitHubat commit 0e7ac2a

Compare with similar skills

Moscow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Moscow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Moscow this skillneurofoo/agent-skills119—~541Automated safety check: PassMIT
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Prioritization Framework Advisordeanpeters/Product-Manager-Skills7.2k2 repos~4.2kAutomated safety check: PassCustom licence
Strategic Roadmap Planningdeanpeters/Product-Manager-Skills7.2k2 repos~4.7kAutomated safety check: PassCustom licence
Idea Validatoraakashg/pm-claude-skills112—~2.3kAutomated safety check: PassMIT
Triagejoa23/linear-cli144—~699Automated safety check: PassMIT

Similar skills

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed
  • Prioritization Framework Advisor

    deanpeters/Product-Manager-Skills

    Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.

    7.2k GitHub starsUsed in 2 repos~4.2k tokens
    Product & Project ManagementAuto-check passed
  • Strategic Roadmap Planning

    deanpeters/Product-Manager-Skills

    Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.

    7.2k GitHub starsUsed in 2 repos~4.7k tokens
    Product & Project ManagementAuto-check passed
  • Idea Validator

    aakashg/pm-claude-skills

    A skill your agent uses when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.

    112 GitHub stars~2.3k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed
  • Triage

    joa23/linear-cli

    Triage and prioritize Linear backlog issues using the linear CLI.

    144 GitHub stars~699 tokensUpdated 24 days ago
    Product & Project ManagementAuto-check passed
  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    715 GitHub stars~1.1k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

More from neurofoo/agent-skills

All 22 skills in this repo
  • Five Whys Analysis

    neurofoo/agent-skills

    Runs a Five Whys root cause analysis, asking why repeatedly from the stated problem until it reaches an actionable cause, then lists corrective actions and verification.

    119 GitHub starsUsed in 1 repo~875 tokens
    Auto-check passed
  • Eisenhower Matrix Prioritizer

    neurofoo/agent-skills

    Sorts a task list into the four Eisenhower quadrants (do, schedule, delegate, eliminate) with reasons, a time distribution check and first actions.

    119 GitHub stars~705 tokensUpdated 8 mo ago
    Auto-check passed
  • OODA Loop Analysis

    neurofoo/agent-skills

    Walks a problem or decision through the OODA loop: observe the facts, orient on causes and assumptions, decide among at least three options, and plan the execution.

    119 GitHub starsUsed in 1 repo~904 tokens
    Auto-check passed
  • Cynefin Problem Classifier

    neurofoo/agent-skills

    Sorts a problem into the Cynefin domains of simple, complicated, complex, chaotic or confused, then recommends a way of working that fits that domain.

    119 GitHub starsUsed in 1 repo~696 tokens
    Auto-check passed
  • Wardley Map Analysis

    neurofoo/agent-skills

    Maps a user need's value chain against evolution stages to guide build-versus-buy decisions and show competitive dynamics.

    119 GitHub stars~776 tokensUpdated 8 mo ago
    Auto-check passed
  • Jtbd

    neurofoo/agent-skills

    Jobs to Be Done analysis to understand what customers really want.

    119 GitHub starsUsed in 1 repo~754 tokens
    Auto-check passed

Questions about Moscow

What does Moscow do?

MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have. Moscow is an agent skill from neurofoo/agent-skills. MoSCoW prioritization categorizing items as Must have, Should have, Could have, or Won't have.

When should I use Moscow?

Moscow fits situations like: scope definition; feature prioritization; everything feels equally important.

How do I install Moscow in Claude Code?

Run `npx skills add neurofoo/agent-skills --skill moscow -a claude-code`. Or copy the skill folder (moscow in neurofoo/agent-skills) into .claude/skills/moscow in your project. Claude Code loads it when a task matches its description.

How do I install Moscow in Codex?

Run `npx skills add neurofoo/agent-skills --skill moscow -a codex`. Or copy the skill folder (moscow in neurofoo/agent-skills) into .agents/skills/moscow in your project. Codex loads it when a task matches its description.

Can I use Moscow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add neurofoo/agent-skills --skill moscow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moscow, .gemini/skills/moscow, .github/skills/moscow and .opencode/skills/moscow in your project.

What does Moscow need to run?

SKILL.md names no scripts, command-line tools or credentials: Moscow is instructions for the agent only.

Does Moscow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Moscow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Moscow use?

Moscow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Moscow use?

About 541 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Moscow?

Skills that share tags, products or a category with Moscow: Agile Product Owner (alirezarezvani/claude-skills, 28k stars), Prioritization Framework Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars) and Idea Validator (aakashg/pm-claude-skills, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Moscow?

neurofoo (a GitHub user) maintains it in neurofoo/agent-skills, which has 119 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on January 19, 2026.

Source: neurofoo/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.