Feature Scope Validator
Validates and clarifies feature requirements before implementation begins, ensuring alignment between stakeholders and developers.
Goal
Clarify requirements
How to Run
Engage with stakeholders through iterative scope refinement until clarity and approval are achieved.
- 01
Provide Initial Prompt
Start by giving a high-level feature idea or requirement to the agent.
- 02
Agent Acts & Reviews
The agent will ask clarifying questions, summarize scope, and wait for stakeholder feedback.
- 03
Iterate Based on Feedback
Repeat the process, adjusting scope based on stakeholder input until approval.
Workflow Steps
- 01
Clarify Requirements
Break down the initial feature request into specific, actionable components.
- 02
Review Scope Feedback
Present the refined scope to stakeholder(s) for validation and comments.
- 03
Incorporate Feedback
Adjust the scope based on stakeholder feedback and unresolved questions.
- 04
Run Scope Check
Execute 'scope review' to validate completeness and alignment.
- 05
Inspect Result
Analyze the outcome of the scope review—approved or requires iteration.
- 06
Repeat or Exit
If not approved, loop back to clarify requirements; if approved, exit the loop.
Kickoff Prompt
Start the "Feature Scope Validator" loop. Goal: Clarify requirements Max iterations: 10 Between iterations run: scope review Exit when: Scope approved I want to build a chat app with user authentication and real-time messaging. Can you help me define the scope clearly? Self-pace this loop. After each iteration, run `scope review` and evaluate the output, and only continue if the exit condition is not met (Scope approved). Stop when the exit condition passes or 10 iterations are reached. Give a short status update each pass.
Guardrails
hardcoded- ·Focus solely on scope definition; do not proceed to design or implementation details.
- ·Require explicit stakeholder confirmation before proceeding to next phase.
- ·Avoid making assumptions—ask targeted questions for every ambiguous requirement.
- ·Maintain neutrality and encourage open discussion during review cycles.
Flow Diagram
Related loops — Planning
Planning
Backlog Grooming Loop
This loop helps your team refine and organize your product backlog by ensuring items are clearly defined, properly prioritized, and ready for development. It iteratively works through backlog items to improve clarity, acceptance criteria, and estimation accuracy.
Planning
Risk Assessment Builder
An automated loop that systematically identifies, analyzes, and documents potential risks in a software project. Designed to help teams proactively manage project threats through structured evaluation cycles.
Planning
Release Planning Loop
A systematic approach to prepare a comprehensive release plan by iteratively assessing project status, identifying risks, and aligning resources. This loop ensures all critical aspects of a software release are covered through automated checks and manual inspections.