refacil-sdd-ai 4.5.2 → 4.5.4

package/README.md

@@ -174,7 +174,7 @@ Some skills delegate their heavy work to **sub-agents** that run in isolated con
 
 **Common properties**: specialized system prompt, direct-invocation guardrail, output contract with a fenced JSON block per skill. Read-only sub-agents (`investigator`, `validator`, `auditor`) do not have `Edit`/`Write`. Write sub-agents (`tester`, `implementer`, `debugger`, `proposer`) do.
 
-**Model**: `refacil-proposer` runs with `model: opusplan` (uses Opus during plan mode for highest-stakes planning, then switches to Sonnet for execution). Other sub-agents use `model: sonnet` by default.
+**Model**: `refacil-proposer` runs with `model: opusplan` (uses Opus during plan mode for highest-stakes planning, then switches to Sonnet for execution). Other sub-agents use `model: sonnet` by default for Claude Code, others use inherit model.
 
 **Triple-platform**: `.claude/agents/refacil-*.md` uses `tools:` (granular allowlist). `.cursor/agents/refacil-*.md` is auto-generated: `readonly: true` for agents without `Edit`/`Write`, `readonly: false` for those that have them; always `model: inherit`. `.opencode/agents/refacil-*.md` is auto-generated via `transformFrontmatterForOpenCode()`: converts `tools:` to a `permission:` block (`edit: allow/deny`, `bash: allow/deny`, `webfetch: deny`), adds `mode: subagent`, adds `hidden: true` for internal agents, and removes `model:`. The installer transforms the frontmatter automatically for all three IDEs.
 

package/agents/proposer.md

@@ -2,7 +2,7 @@
 name: refacil-proposer
 description: Generates SDD-AI planning artifacts (proposal, specs, design, tasks) for any codebase. Delegated by /refacil:propose — do not invoke directly.
 tools: Read, Grep, Glob, Bash, Edit, Write
-model: sonnet
+model: opusplan
 ---
 
 # refacil-proposer — Planning Artifact Generator

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "refacil-sdd-ai",
-  "version": "4.5.2",
+  "version": "4.5.4",
   "description": "SDD-AI: Specification-Driven Development with AI — development methodology using AI with Claude Code, Cursor and OpenCode",
   "bin": {
     "refacil-sdd-ai": "./bin/cli.js"

package/skills/prereqs/METHODOLOGY-CONTRACT.md

@@ -55,24 +55,48 @@ Critical rule:
 
 ### Protocol when the current branch is protected
 
-If the current branch is protected and code needs to be written:
-
-1. **Ask for a task identifier first** — before any git action, ask the user:
-   *"What is the task number or name for this branch? (e.g. SEGINF-20, REF-123, or a short descriptive name)"*
-   Wait for the user's answer before continuing.
-2. Verify clean working directory (`git status --porcelain`).
-3. If there are uncommitted changes, ask for approval to `git stash push -m "auto-stash-refacil"`.
-4. Detect the base branch to create a working branch from:
+If the current branch is protected and code needs to be written, follow the gates below strictly. Each gate is a hard stop — do not proceed to the next gate until the user has replied in the current one.
+
+---
+
+**[GATE 1 — STOP AND WAIT: ask for task identifier]**
+
+Ask the user exactly this question and then STOP. Do NOT run any git command. Do NOT propose a branch name. Do NOT continue to Gate 2 until the user replies:
+
+> "What is the task number or identifier for this branch? (e.g. SEGINF-20, REF-123, or a short descriptive name)"
+
+If the user says they have no ID, note that and proceed to Gate 2 with `<ID> = none`.
+
+---
+
+**[GATE 2 — STOP AND WAIT: propose branch name and ask for approval]**
+
+Only after receiving the user's reply to Gate 1:
+
+1. Verify clean working directory (`git status --porcelain`).
+2. If there are uncommitted changes, ask for approval to stash them (`git stash push -m "auto-stash-refacil"`). Do NOT stash without approval.
+3. Detect the base branch:
    - Prefer `develop`, then `dev`.
    - Only if neither exists (new repo), use `main` or `master` as a temporary exception.
-   - Switch and update (`git pull origin <base>`). If none exist, stop.
-5. **Propose the branch name and wait for explicit user approval before creating it:**
+4. Compose the branch name:
    - Feature: `feature/<ID>` (e.g. `feature/SEGINF-20`)
    - Bugfix: `fix/<ID>` (e.g. `fix/SEGINF-20`)
-   - Without ID: propose a short descriptive name (e.g. `fix/project-root-consistency`) and **require explicit approval** before proceeding.
-   Example: *"I'll create branch `fix/SEGINF-20` from `develop`. Shall I proceed?"*
-6. **Only after explicit user confirmation**: create the branch and restore stash if used.
-7. If the user does not approve at any point, stop.
+   - Without ID: propose a short descriptive name (e.g. `fix/session-timeout-redis`)
+5. Present the proposed name and ask for approval. Then STOP. Do NOT run `git checkout` or `git switch`. Do NOT create the branch yet. Wait for the user's explicit confirmation:
+
+> "I'll create branch `<proposed-name>` from `<base-branch>`. Shall I proceed?"
+
+---
+
+**[GATE 3 — execute only after explicit approval from Gate 2]**
+
+Only after the user explicitly confirms (e.g. "yes", "go", "ok", "proceed"):
+
+1. Switch to the base branch and update it (`git checkout <base>` + `git pull origin <base>`).
+2. Create the working branch (`git checkout -b <branch-name>`).
+3. If a stash was approved in Gate 2, restore it (`git stash pop`).
+
+If the user does not approve at Gate 2, stop entirely. Do not create any branch.
 
 ## §5 — Output policy (UX)