@abarcenas/ai-workflow-template 1.26.0 → 1.28.0

package/.opencode/agents/architect.agent.md

@@ -5,6 +5,7 @@ permission:
   read: allow
   search: allow
   edit: allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-pro
 ---
 
@@ -24,7 +25,7 @@ You are a system architecture specialist focused on designing robust, maintainab
 
 1. **Understand Requirements**: Parse the feature or system requirements from context.
 2. **Explore Existing Architecture**: Read relevant parts of the codebase to understand current patterns.
-3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md` and core `memory-bank/` files (`projectbrief.md`, `activeContext.md`, `systemPatterns.md`, `techContext.md`, `progress.md`) for project context. After completing work, update `memory-bank/activeContext.md` and `memory-bank/progress.md` with architectural decisions made.
+3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md`. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads. After completing work, update `memory-bank/activeContext.md` and `memory-bank/progress.md` with architectural decisions made, then run `memory_bank_memory_update`.
 4. **Design the Solution**: Define components, their responsibilities, and how they interact.
 5. **Document**: Produce architecture documentation covering decisions, rationale, and alternatives.
 

package/.opencode/agents/coder.agent.md

@@ -6,6 +6,7 @@ permission:
   search: "allow"
   edit: "allow"
   execute: "allow"
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-flash
 ---
 
@@ -28,13 +29,14 @@ You are a production code implementation specialist. You write clean, maintainab
    - Read the full phase section for context — understand what sibling tasks exist and how yours fits
    - Check the Parallel Execution Summary to see which batch you belong to and whether sibling tasks are running concurrently
 2. **Explore Context**: Read existing files to understand patterns, conventions, and integration points.
-3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md` and core `memory-bank/` files (`projectbrief.md`, `activeContext.md`, `systemPatterns.md`, `techContext.md`, `progress.md`) for project context.
+3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md`. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads.
 4. **Implement**: Write production code following established patterns.
 5. **Verify**: Check that the implementation compiles/runs correctly.
 6. **Document**: Record what was accomplished in all three locations:
    - **Plan file**: Open `/plan/{purpose}-{component}-{version}.md` and mark your task row's **Completed** column with the current date. If the task is the last incomplete in its phase, update the phase status as well.
    - **memory-bank/activeContext.md**: Append a summary of what was implemented, files changed, and current focus.
    - **memory-bank/progress.md**: Update the project status — document what now works and any known issues.
+   - Run `memory_bank_memory_update` to sync the index.
 
 ## Guidelines
 

package/.opencode/agents/deployer.agent.md

@@ -7,6 +7,7 @@ permission:
   edit: allow
   execute: allow
   "github/*": allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-flash
 ---
 

package/.opencode/agents/designer.agent.md

@@ -5,6 +5,7 @@ permission:
   read: "allow"
   search: "allow"
   edit: "allow"
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-flash
 ---
 
@@ -30,7 +31,7 @@ You are a UI/UX design specialist focused on creating intuitive, accessible, and
 
 1. **Understand Requirements**: Parse the design needs from the prompt or orchestrator context.
 2. **Explore Existing Patterns**: Review existing components, styles, and design tokens in the codebase.
-3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md` and core `memory-bank/` files (`projectbrief.md`, `activeContext.md`, `systemPatterns.md`, `techContext.md`, `progress.md`) for project context. After completing work, update `memory-bank/activeContext.md` and `memory-bank/progress.md` to reflect design changes.
+3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md`. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads. After completing work, update `memory-bank/activeContext.md` and `memory-bank/progress.md` to reflect design changes, then run `memory_bank_memory_update`.
 4. **Check Latest API**: Use Context7 MCP to fetch current TailwindCSS v4+ and daisyUI v5+ APIs before writing markup — avoids deprecated patterns and leverages newest features.
 5. **Design/Implement**: Create or modify UI components following established patterns.
 6. **Validate**: Check for accessibility, responsiveness, and consistency.

package/.opencode/agents/e2e-tester.agent.md

@@ -7,6 +7,7 @@ permission:
   edit: allow
   execute: allow
   "playwright/*": allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-flash
 ---
 

package/.opencode/agents/implementer.agent.md

@@ -6,6 +6,7 @@ permission:
    search: allow
    edit: allow
    execute: allow
+   "memory-bank/*": allow
 model: deepseek/deepseek-v4-pro
 ---
 
@@ -25,7 +26,7 @@ You are an implementation planning specialist. You translate architecture and de
 
 1. **Analyze Input**: Read the architecture doc, design spec, or requirements.
 2. **Explore Codebase**: Understand existing code patterns, conventions, and integration points.
-3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md` and core `memory-bank/` files (`projectbrief.md`, `activeContext.md`, `systemPatterns.md`, `techContext.md`, `progress.md`) for project context. After completing work, update `memory-bank/activeContext.md` and `memory-bank/progress.md` to reflect what was planned.
+3. **Check Memory Bank**: Read `.agents/instructions/memory-bank.instructions.md`. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads. After completing work, update `memory-bank/activeContext.md` and `memory-bank/progress.md` to reflect what was planned, then run `memory_bank_memory_update`.
 4. **Define Tasks**: Break the work into atomic, ordered tasks with:
    - Exact file paths and line numbers
    - Specific changes or additions needed

package/.opencode/agents/orchestrator/feature-pipeline.agent.md

@@ -8,6 +8,7 @@ permission:
   execute: allow
   agent: allow
   todo: allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-pro
 ---
 
@@ -69,7 +70,7 @@ Parse the user's request to determine:
 - Whether autoConfirm mode is requested (check user's message for phrases like "full pipeline", "auto", "go ahead")
 - **Read `.agents/instructions/learned-knowledge.instructions.md`** to apply previously discovered patterns and avoid known pitfalls
 - **Read `docs/.architecture-context.md`** if it exists — it contains the project's auto-detected architecture context (tech stack, layer structure, abstractions, dependency rules) so sub-agents don't rediscover it
-- **Read memory-bank core files**: `memory-bank/projectbrief.md`, `memory-bank/activeContext.md`, `memory-bank/systemPatterns.md`, `memory-bank/techContext.md`, `memory-bank/progress.md` if they exist
+- **Search memory-bank**: use `memory_bank_memory_search` for semantic context and `memory_bank_memory_get` to read core files (`projectbrief.md`, `activeContext.md`, `systemPatterns.md`, `techContext.md`, `progress.md`)
 
 ### Step 2: Initialize Log
 
@@ -107,7 +108,7 @@ IMPORTANT:
 - Previous step context: {previous_step_summary}
 - Architecture context: read docs/.architecture-context.md for tech stack, layer structure, and dependency rules.
 - Learned knowledge: read .agents/instructions/learned-knowledge.instructions.md for patterns and conventions.
-- Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Read `memory-bank/activeContext.md` and `memory-bank/progress.md` for current state. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant.
+- Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant, then run `memory_bank_memory_update`.
 - Return a clear summary (actions taken + files produced/modified + issues).
 ```
 
@@ -140,7 +141,7 @@ When the pipeline reaches the "coder" step and the latest implementer plan has p
       - Work on "Implement task {TASK_ID}: {Description} from plan /plan/{filename}" with base path: "{basePath}".
       - Perform the necessary reads/writes under this base path.
       - Previous step context: {previous_step_summary}
-      - Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Read `memory-bank/activeContext.md` and `memory-bank/progress.md` for current state. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant.
+- Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant, then run `memory_bank_memory_update`.
       - Return a clear summary (actions taken + files produced/modified + issues).
       ```
    d. **Wait for all tasks in this batch to complete** (fan-in). Capture each response summary.

package/.opencode/agents/orchestrator/orchestrator.agent.md

@@ -13,6 +13,7 @@ permission:
   "context7/*": allow
   "github/*": allow
   "playwright/*": allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-pro
 ---
 
@@ -81,7 +82,7 @@ Parse the user's request to determine:
 - Whether autoConfirm mode is requested (check user's message for phrases like "full pipeline", "auto", "go ahead")
 - **Read `.agents/instructions/learned-knowledge.instructions.md`** to apply previously discovered patterns and avoid known pitfalls
 - **Read `docs/.architecture-context.md`** if it exists — it contains the project's auto-detected architecture context (tech stack, layer structure, abstractions, dependency rules) so sub-agents don't rediscover it
-- **Read memory-bank core files**: `memory-bank/projectbrief.md`, `memory-bank/activeContext.md`, `memory-bank/systemPatterns.md`, `memory-bank/techContext.md`, `memory-bank/progress.md` if they exist
+- **Search memory-bank**: use `memory_bank_memory_search` for semantic context and `memory_bank_memory_get` to read core files (`projectbrief.md`, `activeContext.md`, `systemPatterns.md`, `techContext.md`, `progress.md`)
 
 ### Step 2: Build Pipeline
 
@@ -124,7 +125,7 @@ IMPORTANT:
 - Work on "{work_unit}" with base path: "{basePath}".
 - Perform the necessary reads/writes under this base path.
 - Previous step context: {previous_step_summary}
-- Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Read `memory-bank/activeContext.md` and `memory-bank/progress.md` for current state. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant.
+- Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant, then run `memory_bank_memory_update`.
 - Return a clear summary (actions taken + files produced/modified + issues).
 ```
 
@@ -157,7 +158,7 @@ When the pipeline reaches the "coder" step and the latest implementer plan has p
       - Work on "Implement task {TASK_ID}: {Description} from plan /plan/{filename}" with base path: "{basePath}".
       - Perform the necessary reads/writes under this base path.
       - Previous step context: {previous_step_summary}
-      - Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Read `memory-bank/activeContext.md` and `memory-bank/progress.md` for current state. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant.
+      - Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads. After completing work, update `memory-bank/activeContext.md`, `memory-bank/progress.md`, and `memory-bank/tasks/_index.md` if relevant, then run `memory_bank_memory_update`.
       - Return a clear summary (actions taken + files produced/modified + issues).
       ```
    d. **Wait for all tasks in this batch to complete** (fan-in). Capture each response summary.

package/.opencode/agents/orchestrator/tdd-orchestrator.agent.md

@@ -8,6 +8,7 @@ permission:
   execute: allow
   agent: allow
   todo: allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-pro
 ---
 
@@ -93,7 +94,7 @@ Parse the user's request to determine:
 - Whether the user specified `minCoverage` or `maxTDDIterations` overrides (e.g. "minCoverage=85", "maxIterations=5")
 - **Read `.agents/instructions/learned-knowledge.instructions.md`** to apply previously discovered patterns and avoid known pitfalls
 - **Read `docs/.architecture-context.md`** if it exists — it contains the project's auto-detected architecture context (tech stack, layer structure, abstractions, dependency rules) so sub-agents don't rediscover it
-- **Read memory-bank core files**: `memory-bank/projectbrief.md`, `memory-bank/activeContext.md`, `memory-bank/systemPatterns.md`, `memory-bank/techContext.md`, `memory-bank/progress.md` if they exist
+- **Search memory-bank**: use `memory_bank_memory_search` for semantic context and `memory_bank_memory_get` to read core files (`projectbrief.md`, `activeContext.md`, `systemPatterns.md`, `techContext.md`, `progress.md`)
 
 ### Step 2: Build Pipeline
 
@@ -136,8 +137,8 @@ IMPORTANT:
 - The batches within each table must respect dependency order (Batch A has no deps, Batch B depends on Batch A completing, etc.).
 - Architecture context: read docs/.architecture-context.md for tech stack, layer structure, and dependency rules.
 - Learned knowledge: read .agents/instructions/learned-knowledge.instructions.md for patterns and conventions.
-- Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Read `memory-bank/activeContext.md` and `memory-bank/progress.md` for current state.
-- After completing the plan, update `memory-bank/activeContext.md` and `memory-bank/progress.md`.
+- Memory bank: read `.agents/instructions/memory-bank.instructions.md` for task/file conventions. Use `memory_bank_memory_search` for semantic context retrieval and `memory_bank_memory_get` for full file reads.
+- After completing the plan, update `memory-bank/activeContext.md` and `memory-bank/progress.md`, then run `memory_bank_memory_update`.
 - Return a clear summary including: plan file path, number of test tasks, number of implementation tasks, batch breakdown per table.
 ```
 
@@ -173,6 +174,7 @@ IMPORTANT:
      2. Update `memory-bank/tasks/_index.md` — add the new test task entry.
      3. Update `memory-bank/activeContext.md` — append test coverage baseline for this component.
      4. Update `memory-bank/progress.md` — document which test suites were created and their status.
+     5. Run `memory_bank_memory_update` to sync the index.
    - Return a clear summary: test files created, number of test cases per file, coverage areas covered, memory-bank files updated.
    ```
    d. **Wait for all test tasks in this batch to complete** (fan-in). Capture each response summary.
@@ -214,7 +216,8 @@ IMPORTANT:
    - Update memory-bank files:
      1. Update `memory-bank/activeContext.md` — append what was implemented and which tests it satisfies.
      2. Update `memory-bank/progress.md` — document implementation status and test alignment.
-     3. Update the plan file — mark your task row's **Completed** column with the current date.
+     3. Run `memory_bank_memory_update` to sync the index.
+     4. Update the plan file — mark your task row's **Completed** column with the current date.
    - Return a clear summary: files created/modified, which test files were satisfied, build verification results, memory-bank files updated.
    ```
    d. **Wait for all implementation tasks in this batch to complete** (fan-in). Capture each response summary.
@@ -253,6 +256,7 @@ IMPORTANT:
   1. Update `memory-bank/activeContext.md` — append test run results and coverage report.
   2. Update `memory-bank/progress.md` — document verification status.
   3. Update `memory-bank/tasks/_index.md` — update test task statuses based on pass/fail results.
+  4. Run `memory_bank_memory_update` to sync the index.
 - Return a clear summary including: pass/fail counts, coverage percentage, threshold met (yes/no), failing test details if any, coverage gaps if any.
 ```
 

package/.opencode/agents/researcher.agent.md

@@ -8,6 +8,7 @@ permission:
   edit: allow
   "ddg-search/*": allow
   "context7/*": allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-pro
 ---
 

package/.opencode/agents/reviewer.agent.md

@@ -6,6 +6,7 @@ permission:
   search: allow
   edit: allow
   "github/*": allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-flash
 ---
 

package/.opencode/agents/tracker.agent.md

@@ -7,6 +7,7 @@ permission:
   glob: allow
   edit: allow
   write: allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-flash
 ---
 
@@ -19,7 +20,7 @@ You are a documentation specialist. You never write code — you read agent outp
 - Read the orchestrator's log and artifact files from a completed pipeline step
 - Extract what was accomplished, what files were produced, and key decisions
 - Append a structured entry to `docs/tracker-log.md`
-- Append a summary entry to `memory-bank/progress.md` with the same structured information
+- Append a summary entry to `memory-bank/progress.md` with the same structured information, then run `memory_bank_memory_update`
 
 ## Approach
 

package/.opencode/agents/unit-tester.agent.md

@@ -6,6 +6,7 @@ permission:
   search: allow
   edit: allow
   execute: allow
+  "memory-bank/*": allow
 model: deepseek/deepseek-v4-flash
 ---
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@abarcenas/ai-workflow-template",
-  "version": "1.26.0",
-  "description": "A comprehensive template repository for AI-assisted development workflows using OpenCode. Provides structured agent pipelines, TDD orchestrator, memory bank with vector search, skills, prompts, and coding standards distributed as an npm package.",
+  "version": "1.28.0",
+  "description": "A comprehensive template repository for AI-assisted development workflows using GitHub Copilot. This template provides a structured approach to leveraging AI assistance through pre-configured skills, prompts, agents, and coding standards.",
   "main": "index.js",
   "scripts": {
     "test": "playwright test",