maestro-feature

# Maestro Feature Use this for the feature contract and its guarded lifecycle. Tasks deliver the work; QA baseline and slice artifacts prove the feature gates. Activate: `maestro hook record --event skill_activation --skill maestro-feature` ## Use - Author or inspect a feature: `new`, `set`, `show`, `spec`, `list`. - Freeze a proposed contract: `accept`. - Turn an accepted contract into tasks: `prepare`. - Grow a frozen contract: `amend`. - Finish or retire the feature: `ship`, `cancel`, `archive`, `unarchive`. ## Do ```sh maestro feature new "<title>" --description "<d>" # -> proposed maestro feature set <id> --acceptance "<check>" --area "<surface>" maestro feature accept <id> # -> ready, requires qa-baseline maestro feature prepare <id> --draft # reviewable child-task plan maestro feature prepare <id> --from <plan-file> # create/explore/accept tasks maestro feature ship <id> --outcome "<one line>" # -> shipped, requires qa-slice maestro feature archive <id> # terminal features only ``` `set` works only while `proposed`. Repeated base fields replace their full list: `--acceptance`, `--area`, `--non-goal`, `--question`, `--clear-questions`, `--description`, `--request`, `--type`. Use append flags while proposed when adding to an existing list without resending it: `--add-acceptance`, `--add-area`, `--add-non-goal`, `--add-question`. After accept, use `feature amend`. Use `feature show...