baldart 3.22.0 → 3.23.0

package/CHANGELOG.md

@@ -5,6 +5,41 @@ All notable changes to BALDART will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.23.0] - 2026-05-27
+
+Aggiunto il flag `-full` / `--full` a `/new` per espandere un epic ai suoi figli in un colpo solo — `/new FEAT-005 -full` lancia automaticamente `FEAT-005-1`, `FEAT-005-2`, … senza domande di grouping né di branch. Risolve il pattern ricorrente "ho un epic con 5 child card, le voglio tutte ora": prima richiedeva di listarle a mano (`/new FEAT-005-1 FEAT-005-2 FEAT-005-3 …`) o di usare l'hyphen-range solo se gli ID erano numericamente contigui.
+
+### Added — `/new` epic expansion flag
+
+- **[framework/.claude/skills/new/SKILL.md](framework/.claude/skills/new/SKILL.md)**: nuova regola di parsing `Epic expansion (-full / --full)` nella sezione args. Discovery dei figli via union di due rules: (1) filename in `${paths.backlog_dir}` con prefisso `<PARENT-ID>-` (separator letterale, quindi `FEAT-005-1.yml` matcha ma `FEAT-005.yml` e `FEAT-0050.yml` no); (2) cards con `group.parent: <PARENT-ID>`. Il parent stesso è escluso (override esplicito: `/new FEAT-005 FEAT-005 -full`). Ordinamento per `group.sequence` ASC, fallback lessicografico. Batch-scoped: `/new FEAT-005 FEAT-008 -full` espande entrambi gli epic. Zero figli trovati → HALT esplicito (no silent no-op). Mixed batches supportati: `/new FEAT-005 -full FEAT-007` accoda i figli di 005 + FEAT-007 standalone.
+- **[framework/.claude/commands/new.md](framework/.claude/commands/new.md)**: versione condensata della stessa regola, allineata al SKILL canonico.
+
+### Why MINOR (not PATCH)
+
+Capability addition pura: nuovo flag, nessuna modifica al comportamento esistente. Tutti gli invocation pattern pre-3.23 continuano a funzionare identici. Per la decision tree in MAINTAINING.md "Did you add new functionality? → YES → MINOR".
+
+### Why no schema-change propagation
+
+Modifica testuale a due file di skill/command. Zero chiavi nuove in `baldart.config.yml`, zero modifiche CLI (`src/commands/*`), zero hook, zero adapter. La discovery dei figli sfrutta `${paths.backlog_dir}` già presente nella config schema da v3.0.0.
+
+## [3.22.1] - 2026-05-27
+
+Rimosso il gate `AskUserQuestion` di conferma merge introdotto in v3.22.0 Step 7 — era friction inutile contro il "seamless" che è il punto della release. Quando l'utente lancia `/prd` ha già implicitamente accettato la pipeline completa (discovery → design → cards → commit → merge in develop). Chiedere "Procedo con merge?" a fine sessione equivale a chiedere "sei sicuro di voler completare quello che mi hai chiesto di fare?".
+
+### Changed — `/prd` Step 7 merge è ora full-seamless
+
+- **[framework/.claude/skills/prd/references/validation-phase.md](framework/.claude/skills/prd/references/validation-phase.md)**: Step 7 point 9 non è più un `AskUserQuestion` ma una nota che chiarisce il razionale del no-confirmation flow + escape hatch user-initiated ("non mergiare" / "lascia il worktree" honora l'override e ferma dopo il commit).
+- **[framework/.claude/skills/prd/SKILL.md](framework/.claude/skills/prd/SKILL.md)** HARD RULE 17 lifecycle: la descrizione di Step 7 cita "Seamless by default, no confirmation gate" + l'escape hatch.
+- **[framework/.claude/skills/prd/references/discovery-phase.md](framework/.claude/skills/prd/references/discovery-phase.md)**: il messaggio di kickoff visibile all'utente promette esplicitamente "commit + merge automatico in develop + cleanup worktree, seamless" — niente più sorprese a fine sessione.
+
+### Why PATCH and not MINOR
+
+Rimozione di un comportamento (gate di conferma) introdotto solo 0 minuti fa nella stessa giornata. Nessuna nuova capability, nessun breaking change per consumer: il gate non era una feature documentata né attesa dagli utenti pre-v3.22.0, era una sovra-cautela introdotta da me contro la richiesta esplicita ("seamless"). La decision tree di MAINTAINING.md classifica "bugfix di behaviour non desiderato senza breaking change" come PATCH.
+
+### Why no schema-change propagation
+
+Modifica puramente comportamentale dentro un singolo step di una singola skill. Zero chiavi nuove, zero modifiche CLI, zero hook.
+
 ## [3.22.0] - 2026-05-27
 
 Le sessioni `/prd` ora vivono in un **docs worktree** dedicato, esattamente come fa `/new` per le card di codice. Il problema risolto: con 5-10 sessioni Claude in parallelo, ogni PRD inquinava il main checkout con `docs/prd/<slug>/PRD.md`, lo state file, le card YAML, l'eventuale `design.html`, e gli update a `ssot-registry.md` / `project-status.md`. `git status` diventava un campo minato, le sessioni `/new` rischiavano di stashare/committare file PRD non loro, e la review manuale era pressoché impossibile. Soluzione: estendere `worktree-manager` con una **modalità docs lean** (no `npm install`, no porta, no `.env` copy, no build verify, no lint/tsc gates) e integrarla nel ciclo di vita del PRD — creazione automatica al kickoff, merge automatico (previa conferma utente) al termine, cleanup seamless.

package/VERSION

@@ -1 +1 @@
-3.22.0
+3.23.0

package/framework/.claude/commands/new.md

@@ -9,6 +9,7 @@ Parse the card IDs from the arguments. Cards can be specified as:
 - Space-separated: `GLOB-001 GLOB-002 GLOB-003`
 - Hyphen-range: `GLOB-001-GLOB-008` (expands to all cards in range)
 - Comma-separated: `GLOB-001, GLOB-002, GLOB-003`
+- **Epic expansion (`-full` / `--full`)**: `/new <PARENT-ID> -full` (e.g., `/new FEAT-005 -full`) expands to ALL children of the parent epic with **NO questions asked**. Children = YAML files in `backlog/` whose filename starts with `<PARENT-ID>-` (e.g., `FEAT-005-1.yml`, `FEAT-005-2.yml`) OR whose `group.parent` field equals `<PARENT-ID>`. The parent epic card itself is excluded. Sort by `group.sequence` ASC, fallback to lexicographic ID. The flag is batch-scoped (`/new FEAT-005 FEAT-008 -full` expands both). If a parent has zero children → HALT and report. All children share `group.parent`, so the existing worktree logic groups them into ONE worktree under the parent's `git_strategy.branch`.
 
 If no card IDs are provided, ask the user which cards to implement.
 

package/framework/.claude/skills/new/SKILL.md

@@ -23,6 +23,13 @@ Parse the card IDs from the arguments. Cards can be specified as:
 - Space-separated: `GLOB-001 GLOB-002 GLOB-003`
 - Hyphen-range: `GLOB-001-GLOB-008` (expands to all cards in range)
 - Comma-separated: `GLOB-001, GLOB-002, GLOB-003`
+- **Epic expansion (`-full` / `--full`)**: `/new <PARENT-ID> -full` (e.g., `/new FEAT-005 -full`) expands to ALL children of the parent epic with **NO questions asked**. Children discovery — union of two rules:
+  1. YAML files in `${paths.backlog_dir}` whose filename starts with `<PARENT-ID>-` (matches `FEAT-005-1.yml`, `FEAT-005-2.yml`, …; never matches `FEAT-005.yml` itself, never matches `FEAT-0050.yml` because the separator is a literal dash).
+  2. Cards in `${paths.backlog_dir}` whose `group.parent` YAML field equals `<PARENT-ID>` (catches children that don't follow the prefix convention).
+
+  The parent epic card itself is **excluded** (epic parents are typically planning containers; to include it, list it explicitly: `/new FEAT-005 FEAT-005 -full`). Children are sorted by `group.sequence` ASC, falling back to lexicographic ID order. The flag is **batch-scoped**: `/new FEAT-005 FEAT-008 -full` expands BOTH parents. If a `-full` parent has zero discovered children → HALT and report (do not silently no-op). With `-full`, all children share the same `group.parent`, so the existing worktree-grouping logic (pre-flight step 4) places them in ONE worktree under the parent's `git_strategy.branch` — no grouping question is asked.
+
+  Parser contract: strip `-full` / `--full` tokens from the args list, treat each remaining token as a parent ID, and expand via the rules above. Mixed batches are allowed (`/new FEAT-005 -full FEAT-007` queues all children of FEAT-005 PLUS the standalone FEAT-007).
 
 If no card IDs are provided, ask the user which cards to implement.
 

package/framework/.claude/skills/prd/SKILL.md

@@ -133,10 +133,13 @@ message. You ask questions, wait for answers, and iterate.
       `/prd-add`, scan `.worktrees/registry.json` for entries with
       `kind: "docs"` matching the slug; if found, `cd` into that worktree
       before scanning for state files. See [discovery-phase.md](references/discovery-phase.md) § Step 0.
-    - **Step 7 (Commit)** — commit happens inside the worktree, then the skill
-      asks the user for explicit confirmation before invoking `worktree-manager`
-      programmatic `mw-docs`, which rebases onto `origin/develop` and lands the
-      PRD via the configured `git.merge_strategy`. See [validation-phase.md](references/validation-phase.md) § Step 7.
+    - **Step 7 (Commit & Merge)** — commit happens inside the worktree, then
+      `worktree-manager` programmatic `mw-docs` is invoked immediately to
+      rebase onto `origin/develop` and land the PRD via the configured
+      `git.merge_strategy`. Seamless by default, no confirmation gate (the
+      user opted into the full pipeline when they ran `/prd`). If the user
+      explicitly says "non mergiare" / "lascia il worktree", honor the
+      override and stop after the commit. See [validation-phase.md](references/validation-phase.md) § Step 7.
 
     **Path resolution rule (CRITICAL — read carefully).** Claude Code's
     `Write` / `Edit` / `Read` tools require ABSOLUTE paths and **do NOT

package/framework/.claude/skills/prd/references/discovery-phase.md

@@ -116,7 +116,8 @@ Descrizione: <user's description>
 Contesto:    <one-line summary from context-primer>
 
 Tutti i file del PRD vivono nel worktree — il main repo resta pulito.
-Al termine eseguirò un merge automatico in develop (previa tua conferma).
+Al termine commit + merge automatico in develop + cleanup worktree, seamless.
+(Se in qualunque momento mi dici "non mergiare", mi fermo dopo il commit.)
 
 Ora comincio la fase di **Discovery** — ti faro delle domande per capire bene
 la feature prima di scrivere qualsiasi documento.

package/framework/.claude/skills/prd/references/validation-phase.md

@@ -109,27 +109,25 @@ created by Step 1 (HARD RULE 17). `$WORKTREE_PATH` is set in the state file.
 
 ### Merge into develop (worktree-manager mw-docs)
 
-9. **Ask the user for explicit confirmation** before merging — the merge
-   touches `origin/develop` and is hard to reverse. Use `AskUserQuestion`:
-
-   ```
-   PRD pronto per il merge in `develop`.
-
-   Strategia merge:  <pr | local-push>  (da git.merge_strategy)
-   Worktree:         <relative-worktree-path>
-   Branch:           prd/<slug>
-   File:             <N> file (PRD.md, design.html, N card YAML, ...)
-
-   Procedo con merge automatico e cleanup del worktree?
-   ```
-
-   Options:
-   - **Sì, merge e cleanup** (default).
-   - **No, lascia il worktree** — l'utente vuole fare review manuale o test
-     prima del merge. STOP. La sessione finisce qui; il worktree resta su disco
-     pronto per un futuro `/mw` manuale o `worktree-manager mw-docs`.
-
-10. **On confirmation: invoke `worktree-manager` programmatic mw-docs**:
+9. **Invoke `worktree-manager` programmatic mw-docs immediately** — no
+   confirmation prompt. The user opted into the full PRD pipeline when they
+   ran `/prd`; chiedere conferma a fine sessione è friction inutile e rompe
+   il "seamless" che è il punto della v3.22.0.
+
+   The merge is recoverable: if something goes wrong post-merge the user can
+   `git revert` on develop just like any other commit. The hard-to-reverse
+   operations (`git push`, branch deletion) happen inside `mw-docs` which
+   has its own failure handling (rebase abort, push rejection, gh CLI error)
+   — none of which silently corrupts state.
+
+   **Escape hatch.** If the user explicitly says "non mergiare" or "lascia il
+   worktree" at any point during Step 7 (e.g. they want to review the PRD
+   manually before it lands on develop), respect that and STOP after the
+   commit — the worktree stays on disk, ready for a future manual `/mw` or
+   `worktree-manager mw-docs`. This is a user-initiated override, not a
+   default gate.
+
+10. **Invoke `worktree-manager` programmatic mw-docs**:
 
    ```
    Skill: worktree-manager

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "baldart",
-  "version": "3.22.0",
+  "version": "3.23.0",
   "description": "Claude Agent Framework - Reusable framework for coordinating AI agents and humans in software projects",
   "bin": {
     "baldart": "./bin/baldart.js"