product-manage-scope

To track project scope changes and maintain traceability, you need a structured logging system that records the item, direction of change, phase, and rationale. This approach automatically updates your product requirements document to reflect current in-scope and out-of-scope items.

The best way to prevent scope creep is to log scope changes automatically and prompt impact analysis on architecture, stories, and tests whenever features move between in-scope and out-of-scope states, ensuring shifts are fully documented before integration.

To synchronize a PRD when features move out of scope, you must document the rationale for the change and update the centralized project requirements document to accurately reflect the current in-scope and out-of-scope items.

Yes, you need a pre-configured .sweetclaude state directory to log scope changes. This directory maintains consistency across the project lifecycle by serving as the centralized location for tracking and documenting scope movements.

Impact analysis for scope shifts works by prompting you to evaluate ripple effects on architecture, user stories, and tests. This ensures that any feature moving between in-scope and out-of-scope states is assessed for downstream project impact.