Plan feature

Decide what should be built and why. Planning owns product discovery and writes only durable Beads intent; repository specification and authorization belong to /review-feature-spec.

Resolve context

Treat input as an exact ID, slug, title, or new request. Inspect existing Beads features and only the architecture, product docs, source, tests, and related work needed to understand the outcome. Resolve an existing candidate with:

"{baseDir}/../../bin/dstack" ctl feature resolve "<selector>"

Update only one open planned feature labeled dstack:feature-idea and feature:<slug>. Replanning reuses that Beads ID and keeps its established feature:<slug> identity stable; a changed title does not rename the slug. If identity is ambiguous or closed, ask the user. If it is a current molecule, stop and return /review-feature-spec; planning must not change materialized or authorized scope.