@abarcenas/ai-workflow-template 1.47.0 → 1.48.0

package/.agents/config/README.md

@@ -27,10 +27,10 @@ the second calls `grilling` and `domain-modeling` together.
 
 ## Scope agent
 
-`.opencode/agents/scope.agent.md` is the front door for underspecified feature requests. It
+`.opencode/agents/scope.md` is the front door for underspecified feature requests. It
 runs grilling in rounds against a draft file, emits the current frontier as numbered questions,
 and finishes by writing a spike document at `docs/spike-<feature>.md` — the input
-`researcher.agent.md` already expects.
+`researcher.md` already expects.
 
 It never builds or runs code. When a question needs a prototype it emits
 `prototype needed: <question>`, and the orchestrator delegates the work to `coder` (logic) or

package/.agents/instructions/agent.instructions.md

@@ -1,6 +1,6 @@
 ---
 description: "Guidelines for creating custom agent files for opencode"
-applyTo: "**/*.agent.md"
+applyTo: "**/agents/**/*.md"
 ---
 
 # Custom Agent File Guidelines
@@ -11,7 +11,7 @@ Instructions for creating effective and maintainable custom agent files that pro
 
 - Target audience: Developers creating custom agents for opencode
 - File format: Markdown with YAML frontmatter
-- File naming convention: lowercase with hyphens (e.g., `test-specialist.agent.md`)
+- File naming convention: lowercase with hyphens (e.g., `test-specialist.md`)
 - Location: `.opencode/agents/` directory (repository-level)
 - Purpose: Define specialized agents with tailored expertise, tools, and instructions for specific tasks
 - Official documentation: [opencode.ai](https://opencode.ai)
@@ -39,7 +39,7 @@ tools: ["Read", "Edit", "Grep"]
 #### **name** (OPTIONAL)
 
 - Display name for the agent
-- If omitted, defaults to filename (without `.md` or `.agent.md`)
+- If omitted, defaults to filename (without `.md`)
 - Use title case and be descriptive
 - Example: `'Testing Specialist'`
 
@@ -123,7 +123,7 @@ The recommended approach is **prompt-based orchestration**:
 
 - The orchestrator defines a step-by-step workflow in natural language.
 - Each step is delegated to a specialized agent.
-- The orchestrator passes only the essential context (e.g., base path, identifiers) and requires each sub-agent to read its own `.agent.md` spec for tools/constraints.
+- The orchestrator passes only the essential context (e.g., base path, identifiers) and requires each sub-agent to read its own `.md` spec for tools/constraints.
 
 ### How It Works
 
@@ -136,7 +136,7 @@ tools: ["Read", "Edit", "Grep", "Task"]
 2. For each step, invoke a sub-agent by providing:
 
 - **Agent name** (the identifier users select/invoke)
-- **Agent spec path** (the `.agent.md` file to read and follow)
+- **Agent spec path** (the `.md` file to read and follow)
 - **Minimal shared context** (e.g., base path, project name, log file)
 
 ### Prompt Pattern (Recommended)
@@ -147,7 +147,7 @@ Use a consistent "wrapper prompt" for every step so sub-agents behave predictabl
 This phase must be performed as the agent "<AGENT_NAME>" defined in "<AGENT_SPEC_PATH>".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Work on "<WORK_UNIT_NAME>" with base path: "<BASE_PATH>".
 - Perform the necessary reads/writes under this base path.
 - Return a clear summary (actions taken + files produced/modified + issues).
@@ -191,7 +191,7 @@ Structure each step invocation with:
 ```text
 Step 1: Transform raw input data
 Agent: data-processor
-Spec: .opencode/agents/data-processor.agent.md
+Spec: .opencode/agents/data-processor.md
 Context: projectName, basePath
 Input: basePath/raw/
 Output: basePath/processed/
@@ -199,7 +199,7 @@ Expected: write basePath/processed/summary.md
 
 Step 2: Analyze processed data (depends on Step 1 output)
 Agent: data-analyst
-Spec: .opencode/agents/data-analyst.agent.md
+Spec: .opencode/agents/data-analyst.md
 Context: projectName, basePath
 Input: basePath/processed/
 Output: basePath/analysis/
@@ -363,10 +363,10 @@ When invoking a sub-agent, pass all context through descriptive instructions in
 Example (prompt template):
 
 ```text
-This phase must be performed as the agent "documentation-writer" defined in ".opencode/agents/documentation-writer.agent.md".
+This phase must be performed as the agent "documentation-writer" defined in ".opencode/agents/documentation-writer.md".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec.
+- Read and apply the entire agent spec file.
 - Project: [project name]
 - Base path: [base path]
 - Input: [input path]
@@ -389,24 +389,24 @@ Example of a simple orchestrator that validates code through multiple specialize
    - Repository name, PR number
    - Base path
 
-2. Invoke specialized agents sequentially (each agent reads its own `.agent.md` spec):
+2. Invoke specialized agents sequentially (each agent reads its own `.md` spec):
 
 ```text
 Step 1: Security Review
 Agent: security-reviewer
-Spec: .opencode/agents/security-reviewer.agent.md
+Spec: .opencode/agents/security-reviewer.md
 Context: repository name, PR number, base path
 Output: security-review.md
 
 Step 2: Test Coverage
 Agent: test-coverage
-Spec: .opencode/agents/test-coverage.agent.md
+Spec: .opencode/agents/test-coverage.md
 Context: repository name, PR number, base path
 Output: coverage-report.md
 
 Step 3: Aggregate
 Agent: review-aggregator
-Spec: .opencode/agents/review-aggregator.agent.md
+Spec: .opencode/agents/review-aggregator.md
 Context: repository name, PR number, base path
 Output: final-review.md
 ```
@@ -462,7 +462,7 @@ Use consistent variable naming conventions:
 
 ### Naming Conventions
 
-- Use lowercase with hyphens: `test-specialist.agent.md`
+- Use lowercase with hyphens: `test-specialist.md`
 - Name should reflect agent purpose
 - Filename becomes default agent name (if `name` not specified)
 - Allowed characters: `.`, `-`, `_`, `a-z`, `A-Z`, `0-9`
@@ -493,7 +493,7 @@ Use consistent variable naming conventions:
 - [ ] Filename follows lowercase-with-hyphens convention
 - [ ] File placed in correct directory (`.opencode/agents/`)
 - [ ] Filename uses only allowed characters
-- [ ] File extension is `.agent.md`
+- [ ] File extension is `.md`
 
 ### Quality Assurance
 

package/.agents/instructions/context7.instructions.md

@@ -107,3 +107,43 @@ If Context7 cannot find a reliable source:
 
 - Never request or echo API keys. If configuration requires a key, instruct storing it in environment variables.
 - Treat retrieved docs as **helpful but not infallible**; for security-sensitive code, prefer official vendor docs and add an explicit verification step.
+
+## Configuration & troubleshooting (opencode)
+
+opencode substitutes only two forms inside config files:
+
+- `{env:VARIABLE_NAME}` — an **unset variable becomes an empty string**, which fails silently
+- `{file:path/to/file}` — file contents; `~` is supported
+
+It does **not** understand shell-style `$VARIABLE`. Writing `"CONTEXT7_API_KEY": "$CONTEXT7_TOKEN"` sends the literal text `$CONTEXT7_TOKEN` as the header value. The server accepts it at `initialize` and only rejects it at the first tool call, so the MCP reports as *connected* while every tool fails with an invalid-key error.
+
+A valid remote entry:
+
+```json
+"context7": {
+  "type": "remote",
+  "url": "https://mcp.context7.com/mcp",
+  "headers": { "CONTEXT7_API_KEY": "{env:CONTEXT7_TOKEN}" },
+  "enabled": true
+}
+```
+
+### Local servers differ in shape
+
+`McpLocalConfig` requires `command` to be an **array** and the env object to be named `environment`. There is no `args` key and no `env` key — using either makes opencode log `skipped malformed recognized value` and the server never appears in the tool list at all.
+
+```json
+"github": {
+  "type": "local",
+  "command": ["npx", "-y", "@modelcontextprotocol/server-github"],
+  "environment": { "GITHUB_PERSONAL_ACCESS_TOKEN": "{env:GITHUB_PERSONAL_ACCESS_TOKEN}" },
+  "enabled": true
+}
+```
+
+### Diagnosing a dead server
+
+1. Test the credential directly before touching config — `curl` the endpoint, or run the CLI that owns the token. This separates "bad key" from "key never arrived".
+2. Read `~/.local/share/opencode/log/opencode.log` and look for `mcp connected server=<name>` versus `skipped malformed`.
+3. Prefer `{file:~/.config/opencode/secrets/<name>}` when opencode may not be launched from an interactive shell: variables exported in `~/.zshrc` are visible only to interactive zsh sessions, so GUI-launched sessions see nothing.
+4. A private-repo 404 (GitHub) or a 422 from search usually means the MCP is running **anonymous**, not that the resource is missing.

package/.agents/instructions/memory-bank.instructions.md

@@ -136,10 +136,10 @@ All `memory-bank/**/*.md` files must have YAML frontmatter for search indexing.
 
 Scope comes before planning. Underspecified work enters through the `scope` agent; planning starts only once the request is narrowed.
 
-1. **Scope first** — for an underspecified request, the front door is the `scope` agent (`.opencode/agents/scope.agent.md`). It runs grilling rounds against a single draft file, then writes a terminal spike document at `docs/spike-<feature>.md`.
-2. **Hand the spike to research** — that spike document is the input `researcher.agent.md` expects; pass its path as the required spike argument.
+1. **Scope first** — for an underspecified request, the front door is the `scope` agent (`.opencode/agents/scope.md`). It runs grilling rounds against a single draft file, then writes a terminal spike document at `docs/spike-<feature>.md`.
+2. **Hand the spike to research** — that spike document is the input `researcher.md` expects; pass its path as the required spike argument.
 3. **Continue the pipeline** — after research (or directly, when no research is needed), the work continues to `implementer`, `architect`, or `coder`, following the recommended next step recorded in the spike.
-4. **Deep planning is optional** — `plan.agent.md` remains available as an optional deep-planning mode for work that is already scoped. It is demoted in the default flow, not removed or deprecated.
+4. **Deep planning is optional** — `planner.md` remains available as an optional deep-planning mode for work that is already scoped. It is demoted in the default flow, not removed or deprecated.
 
 When scope runs, record the spike document in the memory bank (a task entry in `tasks/` and/or `activeContext.md`) before implementation planning begins, so the settled and deferred decisions survive a session reset.
 

package/.opencode/agents/{architect.agent.md → architect.md}

@@ -1,11 +1,10 @@
 ---
 description: "System architecture and design specialist. Designs component architecture, data flow, module boundaries, and technical strategy. Produces architecture decision records and design documents."
-name: "Architect - System Design"
-permission:
-  read: allow
-  search: allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: deny }
 ---
 
 # Architect - System Design

package/.opencode/agents/{coder.agent.md → coder.md}

@@ -1,13 +1,9 @@
 ---
 description: "Production code implementation specialist. Writes clean, maintainable, well-tested code following project conventions. Implements features, fixes bugs, and refactors existing code."
-name: "Coder - Implementation"
-permission:
-  read: "allow"
-  search: "allow"
-  edit: "allow"
-  execute: "allow"
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # Coder - Implementation

package/.opencode/agents/{deployer.agent.md → deployer.md}

@@ -1,14 +1,9 @@
 ---
 description: "Deployment and release engineering specialist. Handles CI/CD configuration, deployment scripts, release management, infrastructure as code, and environment setup."
-name: "Deployer - Release Engineering"
-permission:
-  read: allow
-  search: allow
-  edit: allow
-  execute: allow
-  "github/*": allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # Deployer - Release Engineering

package/.opencode/agents/{designer.agent.md → designer.md}

@@ -1,11 +1,10 @@
 ---
 description: "UI/UX design specialist. Handles component layout, visual styling, responsive design, design systems, and user experience considerations."
-name: "Designer - UI/UX"
-permission:
-  read: "allow"
-  search: "allow"
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: deny }
 ---
 
 # Designer - UI/UX

package/.opencode/agents/{e2e-tester.agent.md → e2e-tester.md}

@@ -1,12 +1,9 @@
 ---
 description: "Browser debugging and exploration specialist. Inspects pages, analyzes network, takes screenshots, and investigates UI behavior using Chrome DevTools. Read-only — no code or test creation."
-name: "E2E Tester - Browser Automation"
-permission:
-  read: allow
-  search: allow
-  "chrome-devtools/*": allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: shell, resource: "*",    effect: deny }
 ---
 
 # E2E Tester - Browser Automation

package/.opencode/agents/{implementer.agent.md → implementer.md}

@@ -1,13 +1,9 @@
 ---
 description: "Implementation planning specialist. Translates architecture and design documents into detailed, actionable implementation plans with task breakdowns, file-level specifications, and execution ordering."
-name: "Implementer - Implementation Planning"
-permission:
-   read: allow
-   search: allow
-   edit: allow
-   execute: allow
-   "memory-bank/*": allow
-   "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # Implementer - Implementation Planning

package/.opencode/agents/orchestrator/{feature-pipeline.agent.md → feature-pipeline.md}

@@ -1,13 +1,10 @@
 ---
 description: "Stripped-down feature pipeline orchestrator that runs implementer, designer, coder, and tracker sequentially. Bootstraps architecture context, supports step-by-step confirmation, logs progress, and persists lessons learned."
-name: "Feature Pipeline"
-permission:
-  search: allow
-  read: allow
-  agent: allow
-  todo: allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: primary
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # Feature Pipeline
@@ -26,10 +23,10 @@ You are a lightweight orchestration agent that runs a fixed sequential pipeline:
 
 | Step | Role | Agent File | subagent_type | Purpose |
 |---|---|---|---|---|---|
-| 1 | implementer | `implementer.agent.md` | `implementer` | Translate architecture/design into detailed implementation plans |
-| 2 | designer | `designer.agent.md` | `designer` | UI/UX design specs, component layout — no code |
-| 3 | coder | `coder.agent.md` | `coder` | Write production code, implement features |
-| 4 | tracker | `tracker.agent.md` | `tracker` | Document completed work to `docs/tracker-log.md` |
+| 1 | implementer | `implementer.md` | `implementer` | Translate architecture/design into detailed implementation plans |
+| 2 | designer | `designer.md` | `designer` | UI/UX design specs, component layout — no code |
+| 3 | coder | `coder.md` | `coder` | Write production code, implement features |
+| 4 | tracker | `tracker.md` | `tracker` | Document completed work to `docs/tracker-log.md` |
 
 ## Workflow
 
@@ -40,12 +37,12 @@ Delegate bootstrap checks to a sub-agent. Do NOT read or check any files yoursel
 Invoke a sub-agent (use `subagent_type "implementer"`) to check and bootstrap the project:
 
 ```
-This phase must be performed as the agent "Implementer - Implementation Planning" defined in ".opencode/agents/implementer.agent.md".
+This phase must be performed as the agent "Implementer - Implementation Planning" defined in ".opencode/agents/implementer.md".
 
 BOOTSTRAP CONTEXT - Check and initialize project scaffolding:
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Base path: "{basePath}".
 - Check if `docs/.architecture-context.md` exists with real content.
 - If missing or template-only, run the architecture-blueprint-generator skill by reading ".agents/skills/architecture-blueprint-generator/SKILL.md" and following its instructions to analyze the codebase and generate architecture context.
@@ -96,7 +93,7 @@ For each step:
 This phase must be performed as the agent "{agent_name}" defined in ".opencode/agents/{agent_file}".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Work on "{work_unit}" with base path: "{basePath}".
 - Perform the necessary reads/writes under this base path.
 - Previous step context: {previous_step_summary}
@@ -129,10 +126,10 @@ When the pipeline reaches the "coder" step and the latest implementer plan has p
    b. Log: `"Batch {letter}: launching {N} parallel coder tasks — {task_ids}"`
    c. Launch **one Task tool invocation per task**, all concurrently, using `subagent_type "coder"`:
       ```
-      This phase must be performed as the agent "Coder - Implementation" defined in ".opencode/agents/coder.agent.md".
+      This phase must be performed as the agent "Coder - Implementation" defined in ".opencode/agents/coder.md".
 
       IMPORTANT:
-      - Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+      - Read and apply the entire agent spec file (tools, constraints, quality standards).
       - 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}
@@ -199,12 +196,12 @@ After every pipeline (or at the user's request), delegate to a sub-agent to pers
 Invoke the tracker (use `subagent_type "tracker"`) with the pipeline context:
 
 ```
-This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.agent.md".
+This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.md".
 
 PERSIST LESSONS - Record pipeline knowledge:
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec.
+- Read and apply the entire agent spec file.
 - Base path: "{basePath}".
 - Read the orchestrator log at "docs/.orchestrator-log.md" for the full pipeline record.
 - Append a new "Session" entry to ".agents/instructions/learned-knowledge.instructions.md" with:

package/.opencode/agents/orchestrator/{orchestrator.agent.md → orchestrator.md}

@@ -1,18 +1,10 @@
 ---
 description: "Master orchestration agent that dynamically builds and executes multi-step development pipelines. Analyzes user requests, selects the right sub-agents, delegates work with context, and tracks progress through a shared log. Supports both auto-execute and step-by-step confirmation modes."
-name: "Orchestrator - Multi-Agent Workflow"
-permission:
-  search: allow
-  read: allow
-  agent: allow
-  web: allow
-  todo: allow
-  "ddg-search/*": allow
-  "context7/*": allow
-  "github/*": allow
-  "chrome-devtools/*": allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: primary
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # Orchestrator - Multi-Agent Workflow
@@ -31,17 +23,17 @@ You are a master orchestration agent that coordinates specialized sub-agents to
 
 | Role | Agent File | subagent_type | Typical Tools | When to Deploy |
 |---|---|---|---|---|
-| scope | `scope.agent.md` | `scope` | read, search, edit, skill, question (no `execute` — never builds or runs anything) | Underspecified request, vague or unmeasurable success criteria, unknown boundaries, or an explicit request to narrow scope; runs the scoping interview only — never designs or builds |
-| researcher | `researcher.agent.md` | `researcher` | read, search, web, ddg-search/*, context7/* (read-only — no edit, no execute) | Technical unknowns, library evaluation, spike investigation |
-| architect | `architect.agent.md` | `architect` | read, search (no edit — design docs only) | System design, component architecture, data flow planning |
-| implementer | `implementer.agent.md` | `implementer` | read, search, edit, execute | Translating plans into actionable implementation steps |
-| designer | `designer.agent.md` | `designer` | read, search (no edit — design specs only) | UI/UX design, component layout, styling specs |
-| coder | `coder.agent.md` | `coder` | read, search, edit, execute | Writing production code, implementing features |
-| unit-tester | `unit-tester.agent.md` | `unit-tester` | read, search, edit, execute (test files only — *.spec.ts, *.test.ts) | Unit tests, integration tests, test coverage |
-| e2e-tester | `e2e-tester.agent.md` | `e2e-tester` | read, search, chrome-devtools/* | Debugging, exploration, page inspection via Chrome DevTools |
-| reviewer | `reviewer.agent.md` | `reviewer` | read, search, github/* | Code review, security audit, quality gates |
-| deployer | `deployer.agent.md` | `deployer` | read, search, edit, execute, github/* | CI/CD configuration, deployment scripts, release management |
-| tracker | `tracker.agent.md` | `tracker` | read, search | Doc recording — runs after pipeline to log finished work to docs/tracker-log.md |
+| scope | `scope.md` | `scope` | read, search, edit, skill, question (no `execute` — never builds or runs anything) | Underspecified request, vague or unmeasurable success criteria, unknown boundaries, or an explicit request to narrow scope; runs the scoping interview only — never designs or builds |
+| researcher | `researcher.md` | `researcher` | read, search, web, ddg-search/*, context7/* (read-only — no edit, no execute) | Technical unknowns, library evaluation, spike investigation |
+| architect | `architect.md` | `architect` | read, search (no edit — design docs only) | System design, component architecture, data flow planning |
+| implementer | `implementer.md` | `implementer` | read, search, edit, execute | Translating plans into actionable implementation steps |
+| designer | `designer.md` | `designer` | read, search (no edit — design specs only) | UI/UX design, component layout, styling specs |
+| coder | `coder.md` | `coder` | read, search, edit, execute | Writing production code, implementing features |
+| unit-tester | `unit-tester.md` | `unit-tester` | read, search, edit, execute (test files only — *.spec.ts, *.test.ts) | Unit tests, integration tests, test coverage |
+| e2e-tester | `e2e-tester.md` | `e2e-tester` | read, search, chrome-devtools/* | Debugging, exploration, page inspection via Chrome DevTools |
+| reviewer | `reviewer.md` | `reviewer` | read, search, github/* | Code review, security audit, quality gates |
+| deployer | `deployer.md` | `deployer` | read, search, edit, execute, github/* | CI/CD configuration, deployment scripts, release management |
+| tracker | `tracker.md` | `tracker` | read, search | Doc recording — runs after pipeline to log finished work to docs/tracker-log.md |
 
 ## Workflow
 
@@ -52,12 +44,12 @@ Delegate bootstrap checks to a sub-agent. Do NOT read or check any files yoursel
 Invoke a sub-agent (use `subagent_type "implementer"`) to check and bootstrap the project:
 
 ```
-This phase must be performed as the agent "Implementer - Implementation Planning" defined in ".opencode/agents/implementer.agent.md".
+This phase must be performed as the agent "Implementer - Implementation Planning" defined in ".opencode/agents/implementer.md".
 
 BOOTSTRAP CONTEXT - Check and initialize project scaffolding:
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Base path: "{basePath}".
 - Check if `docs/.architecture-context.md` exists with real content.
 - If missing or template-only, run the architecture-blueprint-generator skill by reading ".agents/skills/architecture-blueprint-generator/SKILL.md" and following its instructions to analyze the codebase and generate architecture context.
@@ -137,7 +129,7 @@ For every scope round, the orchestrator must:
 One delegation is one round. Delegate the round with these inputs:
 
 ```text
-Agent: "Scope - Feature Scoping" (.opencode/agents/scope.agent.md)
+Agent: "Scope - Feature Scoping" (.opencode/agents/scope.md)
 work_unit: {feature}
 basePath: {basePath}
 draftPath: docs/spike-<feature>.draft.md
@@ -180,7 +172,7 @@ For each step in the pipeline:
 This phase must be performed as the agent "{agent_name}" defined in ".opencode/agents/{agent_file}".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Work on "{work_unit}" with base path: "{basePath}".
 - Perform the necessary reads/writes under this base path.
 - Previous step context: {previous_step_summary}
@@ -211,10 +203,10 @@ When the pipeline reaches the "coder" step and the implementer's summary include
    b. Log: `"Batch {letter}: launching {N} parallel coder tasks — {task_ids}"`
    c. Launch **one Task tool invocation per task**, all concurrently, using `subagent_type "coder"`:
       ```
-      This phase must be performed as the agent "Coder - Implementation" defined in ".opencode/agents/coder.agent.md".
+      This phase must be performed as the agent "Coder - Implementation" defined in ".opencode/agents/coder.md".
 
       IMPORTANT:
-      - Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+      - Read and apply the entire agent spec file (tools, constraints, quality standards).
       - 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}
@@ -239,10 +231,10 @@ After the pipeline finishes executing (all steps complete or a required step fai
 1. Invoke the tracker using the Task tool with subagent_type "tracker":
 
 ```
-This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.agent.md".
+This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.md".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Base path: "{basePath}".
 - Read the orchestrator log at "docs/.orchestrator-log.md" for the full pipeline record.
 - Read any artifact files referenced in the log.
@@ -300,12 +292,12 @@ After every pipeline (or at the user's request), delegate to a sub-agent to pers
 Invoke the tracker (use `subagent_type "tracker"`) with the pipeline context:
 
 ```
-This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.agent.md".
+This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.md".
 
 PERSIST LESSONS - Record pipeline knowledge:
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec.
+- Read and apply the entire agent spec file.
 - Base path: "{basePath}".
 - Read the orchestrator log at "docs/.orchestrator-log.md" for the full pipeline record.
 - Append a new "Session" entry to ".agents/instructions/learned-knowledge.instructions.md" with:

package/.opencode/agents/orchestrator/{tdd-orchestrator.agent.md → tdd-orchestrator.md}

@@ -1,13 +1,10 @@
 ---
 description: "Test-Driven Development orchestrator that enforces a RED-GREEN-REFACTOR pipeline. Writes tests first via unit-tester, then implements code via coder, verifies coverage ≥90%, and returns to test-writing if thresholds are not met. Tracks all test suites in memory-bank."
-name: "TDD Orchestrator - Test-Driven Development"
-permission:
-  search: allow
-  read: allow
-  agent: allow
-  todo: allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: primary
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # TDD Orchestrator - Test-Driven Development
@@ -28,11 +25,11 @@ You are a Test-Driven Development orchestration agent that enforces a strict RED
 
 | Role | Agent File | subagent_type | Typical Tools | When to Deploy |
 |---|---|---|---|---|---|
-| implementer | `implementer.agent.md` | `implementer` | read, search, edit, execute | Translating requirements into implementation plans with test/code batch tables |
-| unit-tester | `unit-tester.agent.md` | `unit-tester` | read, search, edit (test files only), execute | RED phase: write failing tests. VERIFY phase: run tests + check coverage |
-| coder | `coder.agent.md` | `coder` | read, search, edit, execute | GREEN phase: write minimal production code to pass tests |
-| reviewer | `reviewer.agent.md` | `reviewer` | read, search, github/* | Code review, security audit, quality gates on both tests and implementation |
-| tracker | `tracker.agent.md` | `tracker` | read, search | Doc recording — runs after pipeline to log finished work |
+| implementer | `implementer.md` | `implementer` | read, search, edit, execute | Translating requirements into implementation plans with test/code batch tables |
+| unit-tester | `unit-tester.md` | `unit-tester` | read, search, edit (test files only), execute | RED phase: write failing tests. VERIFY phase: run tests + check coverage |
+| coder | `coder.md` | `coder` | read, search, edit, execute | GREEN phase: write minimal production code to pass tests |
+| reviewer | `reviewer.md` | `reviewer` | read, search, github/* | Code review, security audit, quality gates on both tests and implementation |
+| tracker | `tracker.md` | `tracker` | read, search | Doc recording — runs after pipeline to log finished work |
 
 ## TDD Pipeline Overview
 
@@ -63,12 +60,12 @@ Delegate bootstrap checks to a sub-agent. Do NOT read or check any files yoursel
 Invoke a sub-agent (use `subagent_type "implementer"`) to check and bootstrap the project:
 
 ```
-This phase must be performed as the agent "Implementer - Implementation Planning" defined in ".opencode/agents/implementer.agent.md".
+This phase must be performed as the agent "Implementer - Implementation Planning" defined in ".opencode/agents/implementer.md".
 
 BOOTSTRAP CONTEXT - Check and initialize project scaffolding:
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Base path: "{basePath}".
 - Check if `docs/.architecture-context.md` exists with real content.
 - If missing or template-only, run the architecture-blueprint-generator skill by reading ".agents/skills/architecture-blueprint-generator/SKILL.md" and following its instructions to analyze the codebase and generate architecture context.
@@ -120,10 +117,10 @@ The implementer creates the plan document with **two separate batch tables** for
 3. Invoke the sub-agent using the Task tool with `subagent_type "implementer"`:
 
 ```
-This phase must be performed as the agent "Implementation Plan Generation" defined in ".opencode/agents/implementer.agent.md".
+This phase must be performed as the agent "Implementation Plan Generation" defined in ".opencode/agents/implementer.md".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Work on "{work_unit}" with base path: "{basePath}".
 - Produce a plan file in /plan/ with TWO separate batch execution tables:
   1. **Test Batch Summary** — tasks for writing tests (unit-tester work). Each test task must specify: the test file to create, the component/function under test, expected behaviors to cover, and dependencies on other test tasks.
@@ -153,10 +150,10 @@ IMPORTANT:
    b. Log: `"Test Batch {letter}: launching {N} parallel unit-tester tasks — {task_ids}"`
    c. Launch **one Task tool invocation per test task**, all concurrently, using `subagent_type "unit-tester"`:
    ```
-   This phase must be performed as the agent "Unit Tester - Test Coverage" defined in ".opencode/agents/unit-tester.agent.md".
+   This phase must be performed as the agent "Unit Tester - Test Coverage" defined in ".opencode/agents/unit-tester.md".
 
    IMPORTANT:
-   - Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+   - Read and apply the entire agent spec file (tools, constraints, quality standards).
    - TDD CONTEXT: This is the RED phase. You are writing tests that define expected behavior BEFORE any implementation code exists. These tests SHOULD fail when run — that is correct and expected in TDD.
    - Knowledge retrieval: read `.agents/instructions/knowledge-retrieval.instructions.md` for the mandatory 3-layer protocol (memory-bank + learned-knowledge + knowledgebase_search with graceful failure). Report whether knowledgebase_search was executed or skipped in your final summary.
    - Work on "Write tests for task {TASK_ID}: {Description} from plan /plan/{filename}" with base path: "{basePath}".
@@ -197,10 +194,10 @@ IMPORTANT:
    b. Log: `"Impl Batch {letter}: launching {N} parallel coder tasks — {task_ids}"`
    c. Launch **one Task tool invocation per implementation task**, all concurrently, using `subagent_type "coder"`:
    ```
-   This phase must be performed as the agent "Coder - Implementation" defined in ".opencode/agents/coder.agent.md".
+   This phase must be performed as the agent "Coder - Implementation" defined in ".opencode/agents/coder.md".
 
    IMPORTANT:
-   - Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+   - Read and apply the entire agent spec file (tools, constraints, quality standards).
    - TDD CONTEXT: This is the GREEN phase. Write the MINIMAL production code necessary to pass all existing tests. Do NOT add features beyond what the tests specify. The tests were written first and define the contract you must fulfill.
    - Knowledge retrieval: read `.agents/instructions/knowledge-retrieval.instructions.md` for the mandatory 3-layer protocol (memory-bank + learned-knowledge + knowledgebase_search with graceful failure). Report whether knowledgebase_search was executed or skipped in your final summary.
    - Work on "Implement task {TASK_ID}: {Description} from plan /plan/{filename}" with base path: "{basePath}".
@@ -236,10 +233,10 @@ IMPORTANT:
 3. Invoke the sub-agent using the Task tool with `subagent_type "unit-tester"`:
 
 ```
-This phase must be performed as the agent "Unit Tester - Test Coverage" defined in ".opencode/agents/unit-tester.agent.md".
+This phase must be performed as the agent "Unit Tester - Test Coverage" defined in ".opencode/agents/unit-tester.md".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - TDD CONTEXT: This is the VERIFY phase. Run ALL test files in the project. Report:
   - Total tests: {count}
   - Passed: {count}
@@ -276,10 +273,10 @@ Review both test code and implementation code for quality, correctness, and adhe
 3. Invoke the sub-agent using the Task tool with `subagent_type "reviewer"`:
 
 ```
-This phase must be performed as the agent "Reviewer - Code Quality" defined in ".opencode/agents/reviewer.agent.md".
+This phase must be performed as the agent "Reviewer - Code Quality" defined in ".opencode/agents/reviewer.md".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - TDD CONTEXT: Review BOTH the test files and the implementation files. Verify that:
   - Tests are comprehensive and meaningful (not just mocks returning canned values).
   - Implementation is minimal and does not contain untested code paths.
@@ -304,10 +301,10 @@ After the pipeline finishes executing, delegate to the tracker agent to document
 1. Invoke the tracker using the Task tool with subagent_type "tracker":
 
 ```
-This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.agent.md".
+This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.md".
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec (tools, constraints, quality standards).
+- Read and apply the entire agent spec file (tools, constraints, quality standards).
 - Base path: "{basePath}".
 - Read the orchestrator log at "docs/.orchestrator-log.md" for the full pipeline record.
 - Read any artifact files referenced in the log.
@@ -338,12 +335,12 @@ After every pipeline (or at the user's request), delegate to a sub-agent to pers
 Invoke the tracker (use `subagent_type "tracker"`) with the pipeline context:
 
 ```
-This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.agent.md".
+This phase must be performed as the agent "Tracker - Documentation Recorder" defined in ".opencode/agents/tracker.md".
 
 PERSIST LESSONS - Record pipeline knowledge:
 
 IMPORTANT:
-- Read and apply the entire .agent.md spec.
+- Read and apply the entire agent spec file.
 - Base path: "{basePath}".
 - Read the orchestrator log at "docs/.orchestrator-log.md" for the full pipeline record.
 - Append a new "Session" entry to ".agents/instructions/learned-knowledge.instructions.md" with:

package/.opencode/agents/{plan.agent.md → planner.md}

@@ -1,14 +1,9 @@
 ---
 description: "Strategic planning and architecture assistant focused on thoughtful analysis before implementation. Helps developers understand codebases, clarify requirements, and develop comprehensive implementation strategies."
-name: "Plan Mode - Strategic Planning & Architecture"
-permission:
-  read: allow
-  search: allow
-  edit: allow
-  skill: allow
-  question: allow
-  webfetch: allow
-  websearch: allow
+mode: primary
+permissions:
+  - { action: edit,  resource: "*",    effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # Plan Mode - Strategic Planning & Architecture Assistant

package/.opencode/agents/{researcher.agent.md → researcher.md}

@@ -1,14 +1,10 @@
 ---
 description: "Deep-dive research and investigation specialist. Handles technical unknowns, library evaluation, spike validation, and information gathering from documentation, codebases, and web sources."
-name: "Researcher - Technical Investigation"
-permission:
-  read: allow
-  search: allow
-  web: allow
-  "ddg-search/*": allow
-  "context7/*": allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: deny }
 ---
 
 # Technical spike research mode

package/.opencode/agents/{reviewer.agent.md → reviewer.md}

@@ -1,13 +1,10 @@
 ---
 description: "Code review and quality assurance specialist. Reviews code for correctness, security vulnerabilities, performance issues, maintainability, and adherence to project standards."
-name: "Reviewer - Code Quality"
-permission:
-  read: allow
-  search: allow
-  edit: allow
-  "github/*": allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: deny }
 ---
 
 # Reviewer - Code Quality

package/.opencode/agents/{scope.agent.md → scope.md}

@@ -1,14 +1,10 @@
 ---
 description: "Feature scoping specialist. Narrows underspecified feature requests through rounds of numbered questions with recommended answers, then writes a spike document that researcher and implementer can consume."
-name: "Scope - Feature Scoping"
-permission:
-  read: allow
-  search: allow
-  edit: allow
-  skill: allow
-  question: allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: deny }
 ---
 
 # Scope - Feature Scoping

package/.opencode/agents/{tracker.agent.md → tracker.md}

@@ -1,14 +1,10 @@
 ---
 description: "Documentation recorder that reads completed agent outputs and appends structured documentation to docs/<feature>/<agent>.md. Runs once after a pipeline finishes to produce a human-readable record of what was accomplished."
-name: "Tracker - Documentation Recorder"
-permission:
-  read: allow
-  search: allow
-  glob: allow
-  edit: allow
-  write: allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: deny }
+  - { action: edit,  resource: "*.md", effect: allow }
+  - { action: shell, resource: "*",    effect: deny }
 ---
 
 # Tracker - Documentation Recorder

package/.opencode/agents/{unit-tester.agent.md → unit-tester.md}

@@ -1,13 +1,9 @@
 ---
 description: "Unit and integration testing specialist. Writes comprehensive tests, improves coverage, validates edge cases, and ensures code quality through automated testing."
-name: "Unit Tester - Test Coverage"
-permission:
-  read: allow
-  search: allow
-  edit: allow
-  execute: allow
-  "memory-bank/*": allow
-  "knowledgebase/*": allow
+mode: all
+permissions:
+  - { action: edit,  resource: "*",    effect: allow }
+  - { action: shell, resource: "*",    effect: allow }
 ---
 
 # Unit Tester - Test Coverage

package/AGENTS.md

@@ -16,7 +16,7 @@ Put project-specific agent rules in `AGENTS.project.md` at the repository root.
 ## Core Workflow
 
 1. **Understand before acting** — Read relevant instructions from `.agents/instructions/` before working with specific technologies
-2. **Plan before implementing** — Narrow underspecified work with the `scope` agent first, then use the `.opencode/agents/plan.agent.md` (optional deep planning) or `.opencode/agents/implementer.agent.md` patterns for structured work
+2. **Plan before implementing** — Narrow underspecified work with the `scope` agent first, then use the `.opencode/agents/planner.md` (optional deep planning) or `.opencode/agents/implementer.md` patterns for structured work
 3. **Track progress** — Update `memory-bank/activeContext.md` and `memory-bank/progress.md` after each task (see `.agents/instructions/task-implementation.instructions.md`)
 4. **Maintain context** — Keep memory bank files updated (see `.agents/instructions/memory-bank.instructions.md`)
 
@@ -109,9 +109,9 @@ Five skills installed from `mattpocock/skills` (pinned at `v1.3.1`) drive scopin
 
 ### Scope agent
 
-`.opencode/agents/scope.agent.md` is the front door for underspecified work. It runs `grilling` in rounds against a single draft file, emits each round's frontier as numbered questions with a recommended answer per question, and stops when the frontier is empty or the remaining unknowns are explicitly deferred.
+`.opencode/agents/scope.md` is the front door for underspecified work. It runs `grilling` in rounds against a single draft file, emits each round's frontier as numbered questions with a recommended answer per question, and stops when the frontier is empty or the remaining unknowns are explicitly deferred.
 
-It terminates by writing `docs/spike-<feature>.md` — the spike document `.opencode/agents/researcher.agent.md` already expects as its input. From there the work continues to `researcher` (open questions need evidence), `implementer` (scope settled, planning remains), or `architect` (the shape of the system is the open problem).
+It terminates by writing `docs/spike-<feature>.md` — the spike document `.opencode/agents/researcher.md` already expects as its input. From there the work continues to `researcher` (open questions need evidence), `implementer` (scope settled, planning remains), or `architect` (the shape of the system is the open problem).
 
 The agent has no command-execution permission: it never builds, runs, or tests code. When a question can only be settled empirically it emits `prototype needed: <question>` with a branch, and that work is handed off to `coder` (logic) or `designer` (UI).
 
@@ -128,7 +128,7 @@ These agent workflows (from `.opencode/agents/`) define specialized modes of ope
 
 Underspecified work does not start here. The default front door is the **`scope` agent** (see [`## Agent skills`](#agent-skills)): it narrows the request through grilling rounds and writes `docs/spike-<feature>.md`, which is handed to `researcher` when open questions need evidence, or to `implementer` when only planning remains.
 
-`.opencode/agents/plan.agent.md` remains available as an **optional deep-planning mode** for work that is already scoped but needs a step-by-step plan. It is not deleted and not deprecated — it is demoted in the default flow only. When you use it, follow this sequence:
+`.opencode/agents/planner.md` remains available as an **optional deep-planning mode** for work that is already scoped but needs a step-by-step plan. It is not deleted and not deprecated — it is demoted in the default flow only. When you use it, follow this sequence:
 
 1. **Understand the Goal** — Ask clarifying questions about requirements and goals
 2. **Explore Context** — Examine relevant files, components, and systems that will be affected
@@ -180,7 +180,7 @@ Always ask user permission before: creating files, running commands, modifying t
 
 Use this when you want a fixed, opinionated pipeline: **implementer → designer → coder → tracker**. It bootstraps architecture context, supports step-by-step confirmation, logs progress, and persists lessons learned.
 
-The agent file is at `.opencode/agents/orchestrator/feature-pipeline.agent.md`.
+The agent file is at `.opencode/agents/orchestrator/feature-pipeline.md`.
 
 **When to use:** You want a predictable, four-step feature pipeline without dynamic agent selection. The orchestrator agent is more flexible; this is more opinionated.
 
@@ -201,7 +201,7 @@ implementer (PLAN) → unit-tester∥ (RED) → coder∥ (GREEN) → unit-tester
 | 5 | REVIEW | reviewer | Audits tests + code for quality, security, patterns |
 | 6 | DOCUMENT | tracker | Records results to `docs/tracker-log.md` |
 
-The agent file is at `.opencode/agents/orchestrator/tdd-orchestrator.agent.md`.
+The agent file is at `.opencode/agents/orchestrator/tdd-orchestrator.md`.
 
 **When to use:** Any feature, bug fix, or refactor where tests should be written first. The orchestrator automatically selects this pipeline when testable code changes are requested.
 

package/README.md

@@ -120,18 +120,18 @@ AGENTS.project.md   # Project-owned rules (recreated if deleted, never overwritt
 
 | Agent | File | Role |
 | --- | --- | --- |
-| Orchestrator | `.opencode/agents/orchestrator/orchestrator.agent.md` | Master — analyzes requests, builds pipelines, delegates |
-| Scope | `.opencode/agents/scope.agent.md` | Conditional front door for underspecified requests — grilling rounds, then a spike doc |
-| Researcher | `.opencode/agents/researcher.agent.md` | Technical investigation, library evaluation |
-| Architect | `.opencode/agents/architect.agent.md` | System design, component architecture |
-| Implementer | `.opencode/agents/implementer.agent.md` | Translates designs into implementation plans |
-| Designer | `.opencode/agents/designer.agent.md` | UI/UX, styling, responsive design |
-| Coder | `.opencode/agents/coder.agent.md` | Production code implementation |
-| Unit Tester | `.opencode/agents/unit-tester.agent.md` | Unit and integration tests |
-| E2E Tester | `.opencode/agents/e2e-tester.agent.md` | Playwright browser tests |
-| Reviewer | `.opencode/agents/reviewer.agent.md` | Code review, security audit |
-| Deployer | `.opencode/agents/deployer.agent.md` | CI/CD, deployment scripts |
-| Tracker | `.opencode/agents/tracker.agent.md` | Documentation recorder |
+| Orchestrator | `.opencode/agents/orchestrator/orchestrator.md` | Master — analyzes requests, builds pipelines, delegates |
+| Scope | `.opencode/agents/scope.md` | Conditional front door for underspecified requests — grilling rounds, then a spike doc |
+| Researcher | `.opencode/agents/researcher.md` | Technical investigation, library evaluation |
+| Architect | `.opencode/agents/architect.md` | System design, component architecture |
+| Implementer | `.opencode/agents/implementer.md` | Translates designs into implementation plans |
+| Designer | `.opencode/agents/designer.md` | UI/UX, styling, responsive design |
+| Coder | `.opencode/agents/coder.md` | Production code implementation |
+| Unit Tester | `.opencode/agents/unit-tester.md` | Unit and integration tests |
+| E2E Tester | `.opencode/agents/e2e-tester.md` | Playwright browser tests |
+| Reviewer | `.opencode/agents/reviewer.md` | Code review, security audit |
+| Deployer | `.opencode/agents/deployer.md` | CI/CD, deployment scripts |
+| Tracker | `.opencode/agents/tracker.md` | Documentation recorder |
 
 ### How to Use
 

package/opencode.mcp.example.json

@@ -19,10 +19,9 @@
      },
     "github": {
       "type": "local",
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-github"],
-      "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "$GITHUB_PERSONAL_ACCESS_TOKEN"
+      "command": ["npx", "-y", "@modelcontextprotocol/server-github"],
+      "environment": {
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "{env:GITHUB_PERSONAL_ACCESS_TOKEN}"
       },
       "enabled": true
     },
@@ -30,19 +29,19 @@
       "type": "remote",
       "url": "https://mcp.context7.com/mcp",
       "headers": {
-        "CONTEXT7_API_KEY": "YOUR_API_KEY"
+        "CONTEXT7_API_KEY": "{env:CONTEXT7_TOKEN}"
       },
       "enabled": true
     },
     "playwright": {
       "type": "local",
-      "command": "node",
-      "args": ["scripts/mcp/playwright-mcp-launcher.js"],
-      "env": {
-        "HEADLESS": "$HEADLESS",
-        "SLOW_MO": "$SLOW_MO",
-        "VIEWPORT": "$VIEWPORT"
+      "command": ["node", "scripts/mcp/playwright-mcp-launcher.js"],
+      "environment": {
+        "HEADLESS": "{env:HEADLESS}",
+        "SLOW_MO": "{env:SLOW_MO}",
+        "VIEWPORT": "{env:VIEWPORT}"
       },
+      "timeout": 120000,
       "enabled": true
     },
     "example-server": {
@@ -67,6 +66,7 @@
     "mcp-everything_*": "allow",
     "angular-cli_*": "allow",
     "playwright_*": "allow",
+    "context7_*": "allow",
     "memory-bank_*": "allow"
   }
-}
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@abarcenas/ai-workflow-template",
-  "version": "1.47.0",
+  "version": "1.48.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",
   "bin": {