cu-features

Document use-case tasks by reading CASO_USO_N.md and appending extracted backend and frontend tasks into CASOS_FEATURES.md, enforcing strict formatting with IDs, types, complexity, and estimates to ensure no duplicates and consistent project standards.

The best way to track backend DDL and frontend screens is by extracting implementation tasks from the use case file and writing them under the appropriate CU section in CASOS_FEATURES.md, covering endpoints, schedulers, modals, and reusable components.

Task estimation and documentation work by reading a use case file, identifying required backend and frontend implementation tasks, assigning complexity and estimates, and writing the formatted results with unique IDs into the features documentation file.

Yes, you can avoid duplicating tasks when updating the documentation file because the process enforces strict formatting and checks existing entries to ensure no duplicates are appended under the appropriate CU section.

You should include backend components like DDL definitions, triggers, endpoints, integrations, schedulers, and security, alongside frontend components such as screens, modals, conditional behaviors, notifications, and reusable components.

You need to update the features documentation file whenever a new use case is defined in CASO_USO_N.md, extracting its implementation tasks and appending them to the correct CU section to maintain comprehensive project tracking.