uc-add-feature

To add a new feature use case draft, follow an eight-step, file-based workflow that analyzes existing documentation and generates per-step artifacts before consolidating them into a single draft. This ensures ID continuity and domain-model consistency.

Maintaining domain-model consistency when updating design docs requires referencing existing main documents and prior drafts throughout the workflow. This guided process ensures new features align with the current state model and traceability.

The eight-step workflow organizes use case documentation by generating distinct Markdown artifacts for each phase, saving them to specific draft directories, and finally merging them into a single consolidated draft file.

You need a file-based workflow for creating use case drafts when augmenting an existing project with a new feature. It requires explicit per-step artifacts and strict naming conventions to ensure reproducibility and traceability.

You cannot use this workflow if no project exists yet. You must start from a new project initialization skill first, as this workflow specifically requires an existing project to reference for ID continuity and domain-model consistency.

The use case draft process requires explicit per-step artifacts to ensure strict traceability and reproducibility. By saving each step individually before final consolidation, the design process remains controlled and auditable.