feature-evolution

To plan incremental changes without writing code, you input a change description so the system can read existing documentation, classify the change as a tweak, extension, or refactor, and generate a list of related new tasks. It acts as a product architect to ensure minimal impact.

Incremental feature evolution is the process of analyzing modifications to completed features by reading current documentation, classifying the change type, and updating documents incrementally to generate non-redundant tasks without coding.

To generate tasks for a feature extension while avoiding duplicates, the system reads all relevant documentation to understand the current state, classifies the incremental change, and outputs only change-related new tasks while updating existing documents.

Yes, you can use this approach to classify feature modifications. The system adopts a product architect role to categorize incremental changes into tweak, extension, or refactor, ensuring minimal impact before updating documents and generating tasks.

The best way to update product documentation for incremental changes is to analyze the modification, classify it, and apply minimal incremental updates to existing documents while simultaneously generating a change-related task list.

You should not use incremental change analysis when coding or implementation is required, as this approach strictly analyzes and plans modifications, updates documents, and generates tasks without writing any code.