agentleFS
20030419zhanghongyi20030419zhanghongyi/AI-Software-Engineering-Workflow-Template/.claude/skills/mvp-scope-check/SKILL.md

mvp-scope-check

Skill0 starsChanged 6 months agoMITView on GitHub

Define a small MVP scope before implementation starts.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the files above.

    line 39
  2. Distinctive:

    Add success signal, constraints, and testing minimum.

    line 41
  3. Distinctive:

    Ask for Human Owner review and stop.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MVP Scope Check

Purpose

Generate an MVP Scope Artifact for MVP Gate.

When to use

  • Idea Gate passed and scope must be narrowed
  • The user wants an MVP boundary
  • In scope / out of scope is still vague

Read first

  • AI_WORKFLOW.md
  • docs/11_stage_gates.md
  • docs/13_human_gate_and_rollback.md
  • .ai/artifacts/MVP_SCOPE_ARTIFACT_TEMPLATE.md

Inputs

  • Idea Validation Artifact
  • Current requirements
  • Project constraints

Outputs

  • MVP Scope Artifact
  • Decision suggestion: implement / narrow / redesign / pause

Steps

  1. Confirm the task is in MVP Gate.
  2. Read only the files above.
  3. Define one core hypothesis and clear in-scope / out-of-scope lists.
  4. Add success signal, constraints, and testing minimum.
  5. Ask for Human Owner review and stop.

Human review

Human Owner must review the artifact and choose implement, narrow, redesign, or pause.

Stop conditions

  • In scope is unclear
  • Out of scope is unclear
  • MVP success signal is missing
  • File boundary is unclear
  • Rollback thinking is missing
  • User has not approved the decision step
  • Any action would auto commit / push / merge / release

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.