ReddRadar
Agent skill
mvp-scoping
Use this skill when discussing features, planning work, or when users describe what they want to build. Guides MVP thinking - focusing on "what's the minimum to make this work?" rather than comprehensive solutions. Triggers on phrases like "help me think through this feature", "what should we build first?", "how should we scope this?", or any feature planning discussion.
Install this agent skill to your Project
npx add-skill https://github.com/jclfocused/claude-agents/tree/main/custom_plugins/plugins/linear-planning-workflow/skills/mvp-scoping
SKILL.md
MVP Scoping Skill
This skill guides Claude to apply MVP (Minimum Viable Product) thinking during feature discussions and planning conversations.
When to Use
Apply this skill when:
- Users describe a new feature they want to build
- Discussing scope or requirements for upcoming work
- Users ask "what should we build first?" or similar
- Planning conversations before formal issue creation
- Users seem to be over-engineering or gold-plating solutions
- Reviewing feature proposals or specifications
Core Principles
1. Ruthless Prioritization
Ask: "What is the absolute minimum needed for this feature to be functional?"
- Focus on core functionality only
- Defer edge cases to future iterations
- Ship something that works, iterate later
- If in doubt, cut it out
2. Vertical Slices Over Horizontal Layers
Build end-to-end functionality, not isolated layers:
- Good MVP: "Users can create and save a basic profile"
- Bad MVP: "Complete user model with all fields" (no UI, no save)
3. The "Ship Tomorrow" Test
For each requirement, ask: "If we had to ship tomorrow, would this be essential?"
- Essential = Must have for feature to work at all
- Nice-to-have = Can be added in a follow-up
- Polish = Defer until core is proven
4. Explicit Deferrals
Always document what you're NOT doing in a "Deferred" section.
Guiding Questions
When scoping features, ask:
- What's the single most important user outcome?
- What's the simplest way to achieve that outcome?
- What can we remove and still have something useful?
- What assumptions can we validate with this MVP?
- What would embarrass us if we shipped without it? (Only those are essential)
Anti-Patterns to Avoid
Over-Engineering
- Adding configuration for things that could be hardcoded
- Building abstraction layers "for future flexibility"
- Implementing features "while we're in there"
Premature Optimization
- Performance tuning before measuring
- Caching before proving it's needed
- Scaling considerations for v1
Gold-Plating
- Perfect error messages for unlikely scenarios
- Comprehensive validation for internal tools
- Beautiful UI for admin-only features
Integration with Linear Workflow
When this skill influences planning, the resulting Linear issues should:
- Have clear, minimal acceptance criteria
- Include a "Deferred" section documenting what's out of scope
- Focus on vertical slices that could ship independently
- Avoid sub-issues for "nice to have" features
Remember: "Ship the minimum that works."
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
jclfocused/claude-agents
graphite-workflow
Use this skill when working with Graphite (gt) for stacked PRs, using execute-issue-graphite agent, or when the user mentions Graphite, stacking, or gt commands. Ensures proper use of gt commands instead of raw git for stack-aware operations.
jclfocused/claude-agents
vertical-slice-planning
Use this skill when discussing feature breakdown, PR structure, implementation ordering, or how to decompose work. Guides thinking about vertical slices (end-to-end functionality) rather than horizontal layers (all of one layer first). Triggers on "how should we break this down?", "what order should we implement?", "how many PRs?", or decomposition discussions.
jclfocused/claude-agents
issue-writing
Use this skill when writing, reviewing, or discussing issue descriptions, acceptance criteria, or task breakdowns. Ensures consistent, high-quality issue structure that any developer or AI can pick up and execute. Triggers when drafting issues, defining requirements, or when users ask "how should I write this issue?" or "what should the acceptance criteria be?"
jclfocused/claude-agents
atomic-design-planning
Use this skill when discussing UI components, design systems, frontend implementation, or component architecture. Guides thinking about Atomic Design methodology - atoms, molecules, organisms - and promotes component reuse over creation. Triggers on UI/frontend discussions, "what components do we need?", "should I create a new component?", or design system questions.
jclfocused/claude-agents
linear-discipline
Use this skill when discussing code changes, implementation work, feature status, or when starting/completing development tasks. Reminds about Linear issue tracking discipline - always having an issue in progress before writing code, marking work as done, and creating issues for unexpected scope. Triggers when users mention implementing features, writing code, or checking on work status.
jclfocused/claude-agents
example-skill
Example skill - Claude will autonomously use this based on the description. Describe what this skill does and when to use it.
Didn't find tool you were looking for?