Interview project stakeholders to define scope and generate docs/scope.md.
npx skills add https://github.com/zabuuq/sdd-plugin --skill scope-zabuuq
Please help me install this Agent Skill. Skill: scope Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/scope Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill scope-zabuuq
It converts vague startup ideas into a well-defined project scope that can reliably drive the next planning and delivery steps.
Run /sdd:scope and answer the interview questions to produce a scope document for your project.
High-intent search queries and answers about installing and using this skill.
Defining project scope from a messy idea involves running an interview to capture vision, audience, goals, success criteria, and boundaries. This process challenges ambiguous statements to produce a structured scope document that prepares the foundation for product requirements and technical specifications.
The best way to prepare a product requirements document foundation is to conduct a structured interview that sets project boundaries and success criteria. This generates a structured scope document and updates project state to drive subsequent planning and delivery steps.
Interview-driven scope definition handles overly broad boundaries by applying a right-sizing assessment that challenges ambiguous statements. It optionally detects oversized items and defers them to backlog management, helping split what is being built now versus later.
Yes, you can split a large project during scope definition. The process performs a right-sizing assessment to detect when a project is too large, allowing you to defer oversized items to backlog management and focus on the immediate project scope.
You need a structured scope document for technical specification generation during structured planning of software initiatives. It acts as the foundation by capturing the project vision, audience, goals, and boundaries required to reliably drive the next delivery steps.
A limitation of using an interview workflow for project planning is that it requires loading shared guide rules and optionally using seed context. If the project lacks clear initial direction, the boundary-setting pushback may defer critical features to backlog management instead of defining them immediately.
MihaiOnSoftwareLoad user rules from ~/.ai/rules/ in defined order.
1ambdaValidate technical specifications against structured checklists for completeness and consistency.
flowgladManage subscription lifecycles via cancelSubscription, adjustSubscription, uncancelSubscription, and reload.
JohannesKoningsSynthesize active conversation context into structured technical specifications and project requirements.
