detect-existing-artifact

To detect existing artifacts, run a command that scans the active project folder for defined filename patterns. It identifies files like requirement definitions and prompts you to choose how to proceed with them.

To prevent data loss when handling project files, use a guided workflow that offers options to continue, backup, or open and edit existing artifacts. This ensures controlled file operations before any modifications are made.

The best way to manage versioning for requirement documents is by detecting existing artifact files and selecting a backup workflow path. This preserves data integrity by safely storing previous versions before appending new items.

Yes, you can automate appending new items by applying artifact detection to existing markdown files. When a file is detected, the workflow prompts you to choose a continue path to add new content directly.

Yes, artifact detection works with common project management deliverables like requirements, screen lists, and program definitions. It recognizes specific filename patterns and guides the appropriate file handling process.

You should not use automated artifact detection if your project folder lacks standardized filename patterns. The detection mechanism relies on identifying specific artifact file names to trigger the prompt-based handling workflow.