specrails-core 4.3.0 → 4.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specrails-core",
-  "version": "4.3.0",
+  "version": "4.4.0",
   "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

@@ -217,3 +217,11 @@ Guidelines:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty. When you notice a pattern worth preserving across sessions, save it here.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-backend-developer.md

@@ -52,3 +52,11 @@ Guidelines:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-backend-reviewer.md

@@ -137,3 +137,11 @@ What to save:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-developer.md

@@ -49,6 +49,14 @@ When an OpenSpec change is being applied, you:
 4. **Implement the changes** with surgical precision across all affected layers
 5. **Ensure consistency** with the existing codebase style, patterns, and architecture
 
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.
+
 ## Workflow Protocol — Strict TDD
 
 You MUST follow Test-Driven Development. This is non-negotiable. The cycle is: **Red → Green → Refactor**. Never write production code without a failing test first.

package/templates/agents/sr-doc-sync.md

@@ -232,3 +232,11 @@ What to save:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-frontend-developer.md

@@ -46,3 +46,11 @@ Guidelines:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-frontend-reviewer.md

@@ -130,3 +130,11 @@ What to save:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-merge-resolver.md

@@ -180,3 +180,11 @@ MERGE_RESOLUTION_STATUS: UNRESOLVED
 - **Never** run tests, git commands, or make commits.
 - **Always** write the report even if all statuses are LOW_CONFIDENCE.
 - If a file has 0 conflict markers: log it as `NO_CONFLICTS` and skip (do not rewrite the file).
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-performance-reviewer.md

@@ -171,3 +171,11 @@ PERF_STATUS: NO_PERF_IMPACT
 - **Never ask for clarification** — use defaults when config is missing
 - **Never skip performance-sensitive files** — if in doubt, benchmark it
 - **Always update history** after a successful benchmark run
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-reviewer.md

@@ -303,3 +303,11 @@ What to save:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-security-reviewer.md

@@ -176,3 +176,11 @@ What to save:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.

package/templates/agents/sr-test-writer.md

@@ -161,3 +161,11 @@ What to save:
 ## MEMORY.md
 
 Your MEMORY.md is currently empty.
+
+## Tool Selection — Honor Project-Documented MCP Tools
+
+The project's `CLAUDE.md` may list MCP tools made available via plugin systems (e.g., specrails-hub Integrations). Each entry typically declares (a) tool names, (b) when to use them, (c) what they return.
+
+Before defaulting to built-in tools (`Read`, `Grep`, `Bash`, `WebFetch`, etc.), scan that documentation. When a project-documented MCP tool's declared use-case matches your current need, prefer it over the built-in equivalent — the plugin author chose it for a measurable advantage (lower token cost, higher precision, fresher data, semantic awareness, etc.).
+
+Fall back to built-ins when no plugin tool fits, or when the documented tool fails to execute in the current environment.