scope-options

The scope-options skill acts as a product-focused bridge between abstract requirements and concrete technical implementation. Designed for software engineers, it forces a pause in the development lifecycle to ensure that the 'what' and 'why' of a feature are fully vetted before any code is written. By integrating directly into your development workflow, it guides you through a structured intake process that evaluates both business impact and technical feasibility.

• Conducts rapid project structure scans to provide context-aware suggestions.
• Facilitates structured user intake covering feature intent, audience, and success metrics.
• Forces the definition of MVP boundaries and explicitly declared out-of-scope requirements to prevent scope creep.
• Generates 2-5 concrete technical options, complete with product and technical lenses for comparison.
• Provides trade-off analysis including effort, extensibility, and maintenance considerations.
• Includes ASCII UI mockups to visualize proposed frontend or user-facing changes.
• Transitions seamlessly into formal planning modes by outputting a comprehensive 'Planning Context' summary.
• Encourages a product-first mindset, ensuring that technical choices (such as tech stack, system architecture, or dependencies) serve the user's needs rather than just engineering convenience.

Usage notes and practical constraints:

• Invoke using /scope-options whenever you are about to start a new feature or pivot your existing architecture.
• The tool is strictly designed to aid decision-making and does not write code, produce documentation, or provide time estimates.
• It requires active user input during the questioning phase to ensure the generated options are relevant and actionable.
• Always prioritize the MVP approach suggested by the tool to reduce technical debt and increase speed-to-market.
• Use the provided UI mockups to align stakeholders on the expected user journey before committing to a specific technical implementation.