chore(commands): simplify /prerelease confirmation wording

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: nanotaboada

.claude/commands/prerelease.md

@@ -1,13 +1,16 @@
-Run the pre-release checklist for this project:
+Run the pre-release checklist for this project.
+
+**Working style**: propose before acting at every step — do not commit, push,
+open PRs, or create tags until I explicitly confirm. Apply this throughout.
 
 1. **Detect current release and propose next**: Read `CHANGELOG.md` for the
    coach naming convention (A–Z table) and the most recent release heading.
    Run `git tag --sort=-v:refname` to confirm the latest tag. Determine the
    next codename (next letter in the A–Z sequence after the current one) and
    infer the version bump from the `[Unreleased]` section: any entry marked
    BREAKING → MAJOR; entries under Added → MINOR; only Changed/Fixed/Removed
-   → PATCH. Present the proposed `vX.Y.Z-{codename}` and ask me to confirm
-   or override before proceeding. Do not continue until I confirm.
+   → PATCH. Present the proposed `vX.Y.Z-{codename}` and wait for confirmation
+   or override before proceeding.
 
 2. **Verify working tree**: Confirm we are on `master` with a clean working
    tree. Pull latest if behind remote.
@@ -19,24 +22,20 @@ Run the pre-release checklist for this project:
    `[Unreleased]` with all four empty subsections:
    Added / Changed / Fixed / Removed.
 
-5. **Propose commit and ask for confirmation**:
-   `docs(changelog): release vX.Y.Z Codename`
-   Do not commit until I confirm.
+5. **Propose commit**: `docs(changelog): release vX.Y.Z Codename`
 
 6. **After confirmation**: commit the changelog update. Then run `/precommit`
    to execute the full pre-commit checklist (linting, formatting, tests,
    coverage). Only push the branch and open a PR into `master` once all
    checks pass.
 
-7. **Stop and wait for my explicit confirmation** that:
+7. **Stop and wait** for confirmation that:
    - All CI checks have passed
    - CodeRabbit review comments have been addressed
    - The PR has been merged into `master`
-   Do not create or push the tag until I give this confirmation.
 
-8. **After I confirm**: pull `master`, then propose the annotated tag
-   `vX.Y.Z-{codename}` with message `Release X.Y.Z - Codename` and ask for
-   approval. Do not tag until I confirm.
+8. **After confirmation**: pull `master`, then propose the annotated tag
+   `vX.Y.Z-{codename}` with message `Release X.Y.Z - Codename`.
 
 9. **After confirmation**: create and push the tag. The CD pipeline triggers
    automatically.