mvp-scope-check
Skill0 starsChanged 6 months agoMITView on GitHub
Define a small MVP scope before implementation starts.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/ai-coding-rules.mdcCursor rule
- .cursor/rules/architecture-rules.mdcCursor rule
- .cursor/rules/project-rules.mdcCursor rule
- implementation-reportSkill
- launch-checkSkill
- plan-from-issueSkill
- review-artifactSkill
- scale-automation-reviewSkill
- validate-ideaSkill
- implementation-reportSkill
- launch-checkSkill
- mvp-scope-checkSkill
- plan-from-issueSkill
- review-artifactSkill
- scale-automation-reviewSkill
- validate-ideaSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- could be automatic: a setting could enforce it
- Distinctive: line 38
Read the files above.
- Distinctive: line 59
Do not automatically commit, push, merge, release, tag, or force-push unless the user explicitly approves that exact action.
≈ “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.
Files
MVP Scope Check
Purpose
Generate an MVP Scope Artifact for MVP Gate.
When to use
- Idea Gate passed and scope must be narrowed
- In-scope or out-of-scope is still unclear
- The user wants an MVP decision
Required files to read
- 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
- Requirements
- Project constraints
Outputs
- MVP Scope Artifact
- Decision suggestion: implement / narrow / redesign / pause
Steps
- Read the files above.
- Confirm the task is in MVP Gate.
- Define one core hypothesis, clear in-scope / out-of-scope, and a success signal.
- Generate the MVP Scope Artifact.
- Require Human Owner review and stop.
Human review
Human Owner must review the artifact and choose implement, narrow, redesign, or pause.
Stop conditions
- Information is insufficient
- In-scope / out-of-scope is unclear
- MVP success signal is missing
- Rollback thinking is missing
- User has not approved the decision step
- There is any automatic commit / push / merge / release risk
Codex safety rule
Do not automatically commit, push, merge, release, tag, or force-push unless the user explicitly approves that exact action.
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
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.

