set-feature

Organizing planning and implementation artifacts for multiple features requires setting an active feature context. This automatically routes artifacts into feature-specific subfolders, preventing misplacement and confusion in concurrent workflows.

Setting an active feature routes artifacts by writing the active_feature value into the project config. It then automatically creates and uses dedicated subfolders under planning-artifacts and implementation-artifacts for that specific feature slug.

A feature slug is a URL-friendly identifier for your feature. You need to provide a valid feature slug, such as 'admin-panel', to switch the active feature context and trigger the automatic creation of the corresponding planning and implementation folders.

Yes, you can manage multi-feature project artifacts without manual subfolder creation. By providing a feature slug to switch the active feature, the system automatically creates the necessary planning-artifacts and implementation-artifacts subfolders for you.

You should switch the active feature in your project config during feature creation, switching, or inquiry workflows. This ensures subsequent planning and implementation artifacts are routed into the correct feature-specific folders.

When setting the active feature, the system validates the provided feature slug. If the slug is invalid, the operation fails to prevent routing planning and implementation artifacts into incorrect or malformed folder structures.