prepflow-say-no

To prevent feature creep, challenge the scope and complexity of new feature requests before implementation. Evaluate proposals against the project roadmap and current feature status to ensure they align with established goals and maintainable boundaries.

Prioritizing reuse involves identifying opportunities to extend existing components, API endpoints, and established patterns within the codebase. Guide development toward simpler solutions by adapting current functionality rather than building from scratch.

Challenge the reporting module scope by prompting stakeholders to consider if existing data aggregation features can be leveraged or adapted first. Evaluate the request against the project roadmap to ensure it does not introduce unnecessary complexity.

Evaluate the feasibility of a new user authentication system before implementation by questioning its scope and complexity. Check if established patterns or existing endpoints can be extended to maintain project focus and reduce development overhead.

Yes, effective scope management requires checking the project roadmap before adding new functionality. Evaluating feature requests against current project status ensures new additions align with core goals and prevents unnecessary feature creep.