@syntesseraai/opencode-feature-factory 0.10.14 → 0.10.15

package/AGENTS.md

@@ -36,7 +36,8 @@ When work changes behavior, workflows, configuration, operational guidance, or r
 
 ## Preferred Tooling Pattern
 
-- Use `morph-mcp_codebase_search` first for semantic codebase discovery in stage agents; the orchestration-only `feature-factory` agent should delegate discovery work instead of calling it directly.
+- Use codebase-memory MCP graph tools first in stage agents (`codebase-memory-mcp_search_graph`, `codebase-memory-mcp_get_architecture`, `codebase-memory-mcp_trace_call_path`, `codebase-memory-mcp_get_code_snippet`) for discovery, architecture context, and call-path impact analysis.
+- Keep `morph-mcp_codebase_search` as fallback when codebase-memory MCP is unavailable or the repository has not been indexed.
 - Use `read`, `glob`, and `grep` for targeted file inspection.
 - Writable agents should prefer `morph-mcp` `edit_file`, then fallback to native `edit` when needed.
 - Keep `edit` restricted on read-only agents (`planning`, `reviewing`, `ff-research`).

package/README.md

@@ -76,6 +76,8 @@ Each transition carries forward prior-stage context (summary, gate/verdict, acti
 
 Writable stage agents (`building`, `documenting`) prefer Morph MCP `edit_file` and can fallback to native `edit` (and `write` for new files) when needed. Read-only agents keep `edit` disabled.
 
+Stage-agent code discovery is graph-first: planning/building/reviewing/documenting prefer codebase-memory MCP tools (`codebase-memory-mcp_search_graph`, `codebase-memory-mcp_get_architecture`, `codebase-memory-mcp_trace_call_path`, `codebase-memory-mcp_get_code_snippet`) before semantic warp_grep/warpgrep-style fallbacks.
+
 ### Plugin auto-handoff safety net
 
 The plugin now includes an auto-handoff hook that can continue deterministic next steps by reading explicit machine-readable fields from assistant output and dispatching `client.session.prompt(...)`.
@@ -123,6 +125,8 @@ The plugin merges the following MCP servers into global OpenCode config when mis
 - `context7`
 - `morph-mcp`
 
+`codebase-memory-mcp` is currently treated as an optional prerequisite (not auto-provisioned by this plugin) because it commonly requires repository-specific indexing/setup. Stage agents still include morph semantic fallback guidance when codebase-memory MCP is unavailable.
+
 `morph-mcp` is configured as:
 
 ```json

package/agents/building.md

@@ -11,6 +11,11 @@ tools:
   bash: true
   skill: true
   task: true
+  'codebase-memory-mcp_search_graph': true
+  'codebase-memory-mcp_get_architecture': true
+  'codebase-memory-mcp_trace_call_path': true
+  'codebase-memory-mcp_get_code_snippet': true
+  'codebase-memory-mcp_search_code': true
   'morph-mcp_codebase_search': true
 permission:
   skill:
@@ -59,19 +64,22 @@ Fallback policy:
 
 ## Semantic Code Search
 
-Use `morph-mcp_codebase_search` for semantic code search when you need to:
+Use codebase-memory MCP tools first for semantic/structural code search when you need to:
 
-- Find implementations by meaning, not just text matching (e.g., "authentication logic", "database connection handling")
-- Locate related code without knowing exact names or keywords
-- Understand how features work across the codebase
+- Find implementations by meaning with `codebase-memory-mcp_search_graph`
+- Understand package/service boundaries via `codebase-memory-mcp_get_architecture`
+- Trace caller/callee impact with `codebase-memory-mcp_trace_call_path`
+- Read exact source around graph hits with `codebase-memory-mcp_get_code_snippet`
 
-Prefer this over `grep` when searching by concept rather than exact text.
+Prefer this over warp_grep/warpgrep-style search because graph context reduces false positives and improves dependency-aware edits.
 
 Search fallback order:
 
-1. `morph-mcp_codebase_search` for semantic discovery.
-2. `read` to inspect exact implementation details before editing.
-3. `grep` for exact symbol/literal checks when needed.
+1. `codebase-memory-mcp_search_graph` + `codebase-memory-mcp_get_architecture` for discovery.
+2. `codebase-memory-mcp_trace_call_path` / `codebase-memory-mcp_get_code_snippet` for impact and code verification.
+3. `morph-mcp_codebase_search` if codebase-memory MCP is unavailable or unindexed.
+4. `read` to inspect exact implementation details before editing.
+5. `grep` for exact symbol/literal checks when needed.
 
 ## GitHub Workflow Guidance
 

package/agents/documenting.md

@@ -11,6 +11,11 @@ tools:
   bash: false
   skill: true
   task: true
+  'codebase-memory-mcp_search_graph': true
+  'codebase-memory-mcp_get_architecture': true
+  'codebase-memory-mcp_trace_call_path': true
+  'codebase-memory-mcp_get_code_snippet': true
+  'codebase-memory-mcp_search_code': true
   'morph-mcp_codebase_search': true
 permission:
   skill:
@@ -65,13 +70,20 @@ Fallback policy:
 
 ## Semantic Code Search
 
-Use `morph-mcp_codebase_search` to understand how code actually works before documenting it. Search by meaning (e.g., "how are users authenticated", "error handling middleware") rather than exact text.
+Use codebase-memory MCP tools first to understand how code actually works before documenting it.
+
+- `codebase-memory-mcp_search_graph` to locate relevant functions/classes/routes
+- `codebase-memory-mcp_get_architecture` to capture subsystem context accurately
+- `codebase-memory-mcp_trace_call_path` for workflow and dependency narratives
+- `codebase-memory-mcp_get_code_snippet` to verify exact behavior before writing docs
 
 Search fallback order:
 
-1. `morph-mcp_codebase_search` for semantic discovery.
-2. `read` to verify exact behavior before writing docs.
-3. `grep` for exact symbol/literal checks when needed.
+1. `codebase-memory-mcp_search_graph` + `codebase-memory-mcp_get_architecture` for graph-first discovery.
+2. `codebase-memory-mcp_trace_call_path` / `codebase-memory-mcp_get_code_snippet` for behavior confirmation.
+3. `morph-mcp_codebase_search` if codebase-memory MCP is unavailable or the repo is not indexed.
+4. `read` to verify exact behavior before writing docs.
+5. `grep` for exact symbol/literal checks when needed.
 
 ## GitHub Workflow Guidance
 

package/agents/ff-research.md

@@ -9,6 +9,11 @@ tools:
   bash: false
   skill: true
   task: false
+  'codebase-memory-mcp_search_graph': true
+  'codebase-memory-mcp_get_architecture': true
+  'codebase-memory-mcp_trace_call_path': true
+  'codebase-memory-mcp_get_code_snippet': true
+  'codebase-memory-mcp_search_code': true
   'morph-mcp_codebase_search': true
   'morph-mcp_github_codebase_search': true
 permission:
@@ -53,13 +58,19 @@ You have access to powerful external research tools. **Use them proactively:**
 
 ### Semantic Code Search
 
-- **`morph-mcp_codebase_search`** — Search the local codebase by meaning. Use to understand the project's existing patterns before recommending changes.
+- **`codebase-memory-mcp_search_graph`** — Graph-first local discovery for functions/classes/routes and their relationships.
+- **`codebase-memory-mcp_get_architecture`** — High-level package/service map for architectural context.
+- **`codebase-memory-mcp_trace_call_path`** — Call-chain tracing for impact analysis and behavior verification.
+- **`codebase-memory-mcp_get_code_snippet`** — Read exact symbol source after graph discovery.
+- **`morph-mcp_codebase_search`** — Semantic local fallback when graph indexing is unavailable.
 
 Search fallback order for code understanding:
 
-1. `morph-mcp_codebase_search` for semantic discovery in local code.
-2. `morph-mcp_github_codebase_search` for upstream/public GitHub internals when needed.
-3. `gh_grep_searchGitHub` for exact code pattern matching across public repos.
+1. `codebase-memory-mcp_search_graph` + `codebase-memory-mcp_get_architecture` for local graph-first discovery.
+2. `codebase-memory-mcp_trace_call_path` / `codebase-memory-mcp_get_code_snippet` for local behavior verification.
+3. `morph-mcp_codebase_search` for local semantic fallback when graph search is unavailable.
+4. `morph-mcp_github_codebase_search` for upstream/public GitHub internals when needed.
+5. `gh_grep_searchGitHub` for exact code pattern matching across public repos.
 
 ## GitHub Workflow Guidance
 

package/agents/planning.md

@@ -10,6 +10,11 @@ tools:
   bash: false
   skill: true
   task: true
+  'codebase-memory-mcp_search_graph': true
+  'codebase-memory-mcp_get_architecture': true
+  'codebase-memory-mcp_trace_call_path': true
+  'codebase-memory-mcp_get_code_snippet': true
+  'codebase-memory-mcp_search_code': true
   'morph-mcp_codebase_search': true
 permission:
   skill:
@@ -40,19 +45,22 @@ You are a read-only agent — you do not write or edit files.
 
 ## Semantic Code Search
 
-Use `morph-mcp_codebase_search` for semantic code search when planning:
+Use codebase-memory MCP tools first when planning:
 
-- Understand existing architecture by meaning (e.g., "authentication logic", "API routing")
-- Find related implementations before proposing changes
-- Verify assumptions about how code works
+- `codebase-memory-mcp_search_graph` to find candidate functions, classes, and routes
+- `codebase-memory-mcp_get_architecture` for package/service-level orientation
+- `codebase-memory-mcp_trace_call_path` for dependency and impact analysis
+- `codebase-memory-mcp_get_code_snippet` to inspect exact implementation context
 
-Prefer this over `grep` when searching by concept rather than exact text.
+This is preferred over warp_grep/warpgrep-style semantic discovery because graph-aware results surface structural context directly.
 
 Search fallback order:
 
-1. `morph-mcp_codebase_search` for semantic discovery.
-2. `read` to verify relevant source context.
-3. `grep` for exact symbol/literal checks when needed.
+1. `codebase-memory-mcp_search_graph` + `codebase-memory-mcp_get_architecture` for graph-first discovery.
+2. `codebase-memory-mcp_trace_call_path` / `codebase-memory-mcp_get_code_snippet` for call-flow and source verification.
+3. `morph-mcp_codebase_search` if codebase-memory MCP is unavailable or the repository is not indexed yet.
+4. `read` to verify relevant source context.
+5. `grep` for exact symbol/literal checks when needed.
 
 ## GitHub Workflow Guidance
 

package/agents/reviewing.md

@@ -10,6 +10,11 @@ tools:
   bash: false
   skill: true
   task: true
+  'codebase-memory-mcp_search_graph': true
+  'codebase-memory-mcp_get_architecture': true
+  'codebase-memory-mcp_trace_call_path': true
+  'codebase-memory-mcp_get_code_snippet': true
+  'codebase-memory-mcp_search_code': true
   'morph-mcp_codebase_search': true
 permission:
   skill:
@@ -40,19 +45,22 @@ You are a read-only agent — you do not write or edit files.
 
 ## Semantic Code Search
 
-Use `morph-mcp_codebase_search` for semantic code search when reviewing:
+Use codebase-memory MCP tools first when reviewing:
 
-- Search by meaning to find related code (e.g., "input validation", "access control checks")
-- Verify that implementations match architectural patterns across the codebase
-- Find similar code to check for consistency
+- `codebase-memory-mcp_search_graph` to locate related implementations by structure + name pattern
+- `codebase-memory-mcp_get_architecture` to validate subsystem boundaries and coupling
+- `codebase-memory-mcp_trace_call_path` to verify security/validation coverage across call paths
+- `codebase-memory-mcp_get_code_snippet` to inspect concrete evidence for findings
 
-Prefer this over `grep` when searching by concept rather than exact text.
+Prefer this over warp_grep/warpgrep-style search so findings are anchored to graph-aware dependencies, not isolated text matches.
 
 Search fallback order:
 
-1. `morph-mcp_codebase_search` for semantic discovery.
-2. `read` to verify concrete evidence and line references.
-3. `grep` for exact symbol/literal checks when needed.
+1. `codebase-memory-mcp_search_graph` + `codebase-memory-mcp_get_architecture` for discovery and context.
+2. `codebase-memory-mcp_trace_call_path` / `codebase-memory-mcp_get_code_snippet` for evidence collection.
+3. `morph-mcp_codebase_search` if codebase-memory MCP is unavailable or not indexed.
+4. `read` to verify concrete evidence and line references.
+5. `grep` for exact symbol/literal checks when needed.
 
 ## GitHub Workflow Guidance
 

package/dist/mcp-config.d.ts

@@ -2,6 +2,10 @@ type BunShell = any;
 /**
  * Default MCP server configuration to be added by the plugin
  * These servers will be merged into the global OpenCode config.
+ *
+ * Note: codebase-memory-mcp is intentionally not auto-provisioned here.
+ * It is treated as an optional prerequisite because it commonly needs
+ * repository-specific indexing/setup before graph queries are useful.
  */
 export declare const DEFAULT_MCP_SERVERS: {
     readonly 'jina-ai': {

package/dist/mcp-config.js

@@ -2,6 +2,10 @@ import { isRecord, updateGlobalOpenCodeConfigBlock } from './opencode-global-con
 /**
  * Default MCP server configuration to be added by the plugin
  * These servers will be merged into the global OpenCode config.
+ *
+ * Note: codebase-memory-mcp is intentionally not auto-provisioned here.
+ * It is treated as an optional prerequisite because it commonly needs
+ * repository-specific indexing/setup before graph queries are useful.
  */
 export const DEFAULT_MCP_SERVERS = {
     'jina-ai': {

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@syntesseraai/opencode-feature-factory",
-  "version": "0.10.14",
+  "version": "0.10.15",
   "type": "module",
   "description": "OpenCode plugin for Feature Factory agents - provides sub-agents and skills for validation, review, security, and architecture assessment",
   "license": "MIT",