specrails-core 4.6.5 → 4.6.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specrails-core",
-  "version": "4.6.5",
+  "version": "4.6.6",
   "description": "AI agent workflow system for Claude Code — installs 12 specialized agents, orchestration commands, and persona-driven product discovery into any repository",
   "type": "module",
   "bin": {

package/templates/agents/sr-architect.md

@@ -51,21 +51,22 @@ Do not proceed with any design work, file reading, or artifact creation until sp
 
 When invoked by the orchestrator with a specName argument, you must execute the following steps in order:
 
-### Step 0: Scaffold OpenSpec Artifacts
+### Step 0: Scaffold OpenSpec Artifacts (execute `/opsx:ff`)
 
-Before any design work, scaffold the required OpenSpec artifacts for `<specName>` by invoking the OpenSpec fast-forward skill via the Skill tool:
+Your **first action — before any analysis, design, or file writing — MUST be to actually invoke the OpenSpec fast-forward skill via the Skill tool**:
 
 ```
 Skill("opsx:ff", specName)
 ```
 
-`opsx:ff` creates the change directory AND generates `proposal.md`, `design.md`, and `tasks.md` in a single pass.
+This is a real tool call, not a description of intent. Pass `specName` **and** the feature description/context you were given, so `opsx:ff` has everything it needs to run start-to-finish **without prompting**. `opsx:ff` runs `openspec new change` and then generates `proposal.md`, `design.md`, the spec deltas under `specs/`, and `tasks.md` in the **canonical OpenSpec format** (it drives `openspec instructions` per artifact). These files are the single source of truth.
 
-**Critical rules:**
-- You MUST NOT hand-author `proposal.md`, `design.md`, or `tasks.md` — these are produced exclusively by `opsx:ff`
-- Do NOT call `opsx:new` first. `opsx:ff` runs `openspec new change` internally; if the change already exists, that command fails with `Change already exists` and `opsx:ff` aborts. `opsx:ff` alone is the complete scaffold step.
-- `opsx:ff` runs non-interactively — do NOT prompt the user or ask for confirmation at any point
-- Only after Step 0 completes successfully do you proceed to Steps 1–6 below
+**Critical rules — non-negotiable:**
+- You MUST actually call the Skill tool and let `opsx:ff` write the files. You MUST NOT hand-author `proposal.md`, `design.md`, or `tasks.md`, and you MUST NOT emulate or paraphrase what the skill would do — these are produced **exclusively** by `opsx:ff`. A `tasks.md` in any shape other than what `opsx:ff` writes is a defect.
+- If `opsx:ff` appears to need input you cannot provide interactively, make the most reasonable decision from the feature context and continue — do NOT stall, and do NOT fall back to writing the artifacts yourself.
+- Do NOT call `opsx:new` first. `opsx:ff` runs `openspec new change` internally; if the change already exists, that command fails with `Change already exists` and `opsx:ff` aborts. `opsx:ff` alone is the complete scaffold step (idempotent — reuse an existing change).
+- Steps 1–6 below **refine and annotate** the artifacts `opsx:ff` generated and produce your design summary for the orchestrator. They do NOT replace `opsx:ff`'s `tasks.md` with a different structure.
+- Only after Step 0 completes successfully do you proceed to Steps 1–6 below.
 
 ### 1. Analyze Spec Changes
 - Read all relevant specs from `openspec/specs/` — this is the **source of truth**

package/templates/agents/sr-developer.md

@@ -95,13 +95,13 @@ You MUST follow Test-Driven Development. This is non-negotiable. The cycle is: *
 
 ### Phase 3: Implement (TDD cycle)
 
-**Entry point: invoke `/opsx:apply` first.** Before writing any files, invoke the apply skill via the Skill tool:
+**Entry point: your first action in this phase MUST be to actually invoke the apply skill via the Skill tool** — this is a real tool call, not a description of intent:
 
 ```
 Skill("opsx:apply", specName)
 ```
 
-Do NOT write production files directly without first calling `opsx:apply`. The apply command drives the task loop and records task completion state in `tasks.md`.
+`opsx:apply` reads the OpenSpec change context and drives the task loop in `tasks.md`, marking each task `- [x]` as it is implemented. Do NOT write any production files before calling `opsx:apply`, and do NOT emulate it by editing `tasks.md` yourself outside the skill. Pass `specName` so it runs non-interactively; implement each task following the RED → GREEN → REFACTOR cycle below.
 
 **After `opsx:apply` exits — Checkbox Verification Gate:**
 

package/templates/agents/sr-reviewer.md

@@ -121,11 +121,17 @@ After running CI checks, also review for:
    - Search for any lines matching `- [ ]` (hyphen, space, open-bracket, space, close-bracket)
    - **If any `- [ ]` lines are found**: BLOCK archive. List every incomplete task title. Report to orchestrator that archive is blocked — do NOT invoke `/opsx:archive`.
    - **If no `- [ ]` lines remain** (all tasks are `- [x]`): gate passes — proceed to Step 6.
-6. **Archive** — Only reachable when Step 5 gate passes. Invoke the archive skill via the Skill tool:
+6. **Archive** — Only reachable when Step 5 gate passes. Your archive action MUST be a real call to the archive skill via the Skill tool (not a manual directory move, not an emulation):
    ```
    Skill("opsx:archive", specName)
    ```
-   Run non-interactively. Do NOT prompt the user or ask for confirmation.
+   `opsx:archive` must **sync the delta specs** from `openspec/changes/<specName>/specs/` into the main specs under `openspec/specs/` AND move the change to `openspec/changes/archive/`. Pass `specName` so it runs non-interactively; do NOT prompt the user.
+
+   **Verify the archive landed** after the skill returns:
+   - `openspec/changes/<specName>/` no longer exists (the change was moved), and
+   - the delta-spec changes are now present under `openspec/specs/`.
+
+   If either is false, the archive did NOT complete (a common symptom of a *simulated* archive is delta specs that were never synced) — report `archive incomplete` to the orchestrator and do NOT treat the change as done.
 
 ## Write Failure Records