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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/linear-planning-workflow:mvp-scopingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill guides Claude to apply MVP (Minimum Viable Product) thinking during feature discussions and planning conversations.
This skill guides Claude to apply MVP (Minimum Viable Product) thinking during feature discussions and planning conversations.
Apply this skill when:
Ask: "What is the absolute minimum needed for this feature to be functional?"
Build end-to-end functionality, not isolated layers:
For each requirement, ask: "If we had to ship tomorrow, would this be essential?"
Always document what you're NOT doing in a "Deferred" section.
When scoping features, ask:
When this skill influences planning, the resulting Linear issues should:
Remember: "Ship the minimum that works."
npx claudepluginhub jclfocused/claude-agents --plugin linear-planning-workflowScopes a minimum viable product by defining the core hypothesis, triaging features by effort/impact, and producing a 2-week sprint plan with success criteria.
Prevents feature creep with checklists for validating user needs, measuring impact, assessing complexity, defining MVPs, and managing scope in software projects.
Cuts over-engineered plans down to one achievable increment by reading the codebase, identifying core value, and sorting work into keep/defer/drop.