feature-init

To initialize a DAE feature workspace, this Skill creates the required feature folder, Ready contract metadata, branch, and tracker record. It enforces slug rules and validation to ensure your pipeline starts from a well-formed, tracked state.

A Ready contract is the required starting metadata structure created during feature initialization. It ensures your DAE pipeline has a well-formed foundation before any downstream generation like progress, spec, or session logs occurs.

Yes, you can onboard an existing feature into the DAE pipeline by reverse-engineering it into a consistent pipeline-ready state. The Skill handles intake from existing work, applies slug validation, and sets up the tracker record without pre-generating downstream artifacts.

When branch or slug collisions occur during feature initialization, the Skill prevents conflicts by applying promote and redirect rules. It routes you to the correct follow-up skill like feature-edit or feature-promote to resolve the issue safely.

The best way to start greenfield work from a feature intake payload is to use this Skill to run an intake interview if no payload exists, or directly initialize the feature folder, branch, and tracker record if the payload is present.