maestro-design

# Maestro Design Use this when the deliverable is the design of record, not code. The feature stays `proposed` while the contract is still editable; `feature accept` ends design and freezes the contract. Activate: `maestro hook record --event skill_activation --skill maestro-design` ## Do 1. Open one feature for the topic: `maestro feature new "<topic>" --description "<problem>" --question "<loose question>"`. 2. Map the current state from real evidence before options: files, commands, outputs, screenshots, or repo artifacts with `file:line` where code is involved. 3. Put the problem and open questions on the feature: `maestro feature set <id> --description "<problem>" --question "<loose question>"`. 4. Decide one fork at a time. For each fork, give the concrete example, the options, the tradeoff, and the chosen answer. 5. Lock each decision durably: `maestro decision new "<decision title>" --feature <id> --context "<why>"` opens the fork; `maestro decision lock <decision-id> --decision "<chosen>" --rejected "<option: why>" [--preview "<example>"] [--supersedes <id>]` fills and locks it. The lock echoes the entry and appends the dated feature-note pointer automatically; do not add a manual duplicate note. 6. If a chosen answer removes a field, file, command, behavior, or workflow, enumerate consumers before locking the removal. 7. Keep feature questions current: open decisions are for real forks; `--question` is for loose questions not ...