@abarcenas/ai-workflow-template 1.16.0 → 1.18.0

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

@@ -45,3 +45,32 @@ Return a summary covering:
 - Data/control flow between components
 - Files affected or to be created
 - Open questions or risks
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Architect - System Design — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

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

@@ -47,3 +47,32 @@ Return a summary covering:
 - Any deviation from the plan and why
 - Known limitations or follow-up work
 - Build/run verification results
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Coder - Implementation — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

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

@@ -48,3 +48,32 @@ Return a summary covering:
 - Release process documentation
 - Rollback procedures defined
 - Verification results
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Deployer - Release Engineering — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

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

@@ -56,3 +56,32 @@ Return a summary covering:
 - Responsive behavior
 - Files affected
 - Context7 queries performed (which libraries/versions consulted)
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Designer - UI/UX — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

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

@@ -47,3 +47,32 @@ Return a summary covering:
 - Testing patterns used (page objects, fixtures, etc.)
 - Any test configuration changes
 - Known limitations or areas needing manual testing
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: E2E Tester - Browser Automation — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

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

@@ -48,3 +48,32 @@ Return a summary covering:
 - Key implementation decisions
 - Dependencies and ordering
 - Testing requirements identified
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Implementer - Implementation Planning — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

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

@@ -21,6 +21,7 @@ You are a lightweight orchestration agent that runs a fixed sequential pipeline:
 - **basePath**: Root directory for the work (defaults to current workspace)
 - **logFile**: Path to the orchestration log (defaults to `docs/.orchestrator-log.md`)
 - **autoConfirm**: If `true`, execute all pipeline steps without pausing. If `false`, ask the user before each delegation. (Default: `false`)
+- **confirmationGates**: Agents whose output requires mandatory user confirmation before the pipeline advances to the next step. Confirmation is requested *after* the agent produces its output, regardless of `autoConfirm`. Default: `["implementer"]`
 
 ## Sub-Agent Registry
 
@@ -73,15 +74,17 @@ Parse the user's request to determine:
 ### Step 2: Initialize Log
 
 Create or append to the log file at `{logFile}` with:
-- Pipeline plan (implementer → designer → coder → tracker)
+- Pipeline plan (implementer ⏸️ → designer → coder → tracker)
 - AutoConfirm setting
 - Start timestamp
 
+**Note:** ⏸️ marks a *confirmation gate* — the pipeline will pause after that agent's output and wait for user confirmation before proceeding.
+
 ### Step 3: Execute Pipeline
 
 Run the four steps in fixed order:
 
-1. **implementer** — Translates architecture/design into detailed implementation plans
+1. **implementer** ⏸️ — Translates architecture/design into detailed implementation plans
 2. **designer** — Designs UI/UX, component layout, styling
 3. **coder** — Writes production code implementing the feature
 4. **tracker** — Documents completed work to `docs/tracker-log.md`
@@ -109,6 +112,13 @@ IMPORTANT:
 4. Capture the sub-agent's response summary.
 5. Update the log file with: step name, status (SUCCESS/SKIPPED/FAILED), duration, artifacts produced, key findings.
 6. If a required step fails, stop the pipeline and report to the user.
+7. **Confirmation Gate**: If the current agent is in the `confirmationGates` list (default: `["implementer"]`):
+   - Present the agent's output summary (key findings, files produced, artifacts) to the user.
+   - Ask: **"{agent_name} output is ready. Review the summary above. Confirm to proceed to the next step?"**
+   - **Do not advance** to the next pipeline step until the user explicitly confirms.
+   - If the user confirms, log "Confirmation gate passed" in the log file.
+   - If the user rejects, ask: "What would you like to do? Options: (1) Re-run with feedback, (2) Skip this phase, (3) Abort pipeline." Act on their choice.
+   - This gate applies **regardless** of the `autoConfirm` setting — it is a mandatory pause point.
 
 ### Step 4: Present Results
 

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

@@ -26,6 +26,7 @@ You are a master orchestration agent that coordinates specialized sub-agents to
 - **basePath**: Root directory for the work (defaults to current workspace)
 - **logFile**: Path to the orchestration log (defaults to `docs/.orchestrator-log.md`)
 - **autoConfirm**: If `true`, execute all pipeline steps without pausing. If `false`, ask the user before each delegation. (Default: `false`)
+- **confirmationGates**: Agents whose output requires mandatory user confirmation before the pipeline advances to the next step. Confirmation is requested *after* the agent produces its output, regardless of `autoConfirm`. Default: `["researcher", "implementer"]`
 
 ## Sub-Agent Registry
 
@@ -86,14 +87,16 @@ Parse the user's request to determine:
 
 Based on the analysis, build an ordered list of sub-agent delegations. Common patterns:
 
-- **Full feature**: researcher → architect → coder → unit-tester → e2e-tester → reviewer → deployer
+- **Full feature**: researcher ⏸️ → implementer ⏸️ → architect → coder → unit-tester → e2e-tester → reviewer → deployer
 - **Quick fix**: coder → unit-tester → reviewer
-- **Research spike**: researcher → architect
+- **Research spike**: researcher ⏸️ → architect
 - **Refactor**: architect → coder → unit-tester → reviewer
 - **Design task**: designer → reviewer
 - **Test coverage**: unit-tester → e2e-tester
 - **Deployment**: reviewer → deployer
 
+**Note:** ⏸️ marks a *confirmation gate* — the orchestrator will pause after that agent's output and wait for user confirmation before proceeding.
+
 You may skip, reorder, or parallelize steps based on the request. Document your reasoning in the log.
 
 ### Step 3: Initialize Log
@@ -126,6 +129,13 @@ IMPORTANT:
 4. Capture the sub-agent's response summary.
 5. Update the log file with: step name, status (SUCCESS/SKIPPED/FAILED), duration, artifacts produced, key findings.
 6. If a required step fails, stop the pipeline and report to the user.
+7. **Confirmation Gate**: If the current agent is in the `confirmationGates` list (default: `["researcher", "implementer"]`):
+   - Present the agent's output summary (key findings, files produced, artifacts) to the user.
+   - Ask: **"{agent_name} output is ready. Review the summary above. Confirm to proceed to the next step?"**
+   - **Do not advance** to the next pipeline step until the user explicitly confirms.
+   - If the user confirms, log "Confirmation gate passed" in the log file.
+   - If the user rejects, ask: "What would you like to do? Options: (1) Re-run with feedback, (2) Skip this phase, (3) Abort pipeline." Act on their choice.
+   - This gate applies **regardless** of the `autoConfirm` setting — it is a mandatory pause point.
 
 ### Step 5: Record Documentation
 

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

@@ -5,6 +5,7 @@ permission:
   read: allow
   search: allow
   web: allow
+  edit: allow
   "ddg-search/*": allow
   "context7/*": allow
 model: openrouter/kimi-k2-thinking
@@ -209,3 +210,32 @@ Always ask permission for: creating files, running commands, modifying system, e
 
 Transform uncertainty into actionable knowledge through systematic, obsessive, recursive research.
 
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Researcher - Technical Investigation — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.
+

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

@@ -4,6 +4,7 @@ name: "Reviewer - Code Quality"
 permission:
   read: allow
   search: allow
+  edit: allow
   "github/*": allow
 model: openrouter/deepseek-flash-v4
 ---
@@ -44,3 +45,32 @@ Return a summary covering:
 - 🟡 Major findings (should address)
 - 🔵 Minor findings (consider addressing)
 - Overall assessment and recommendation (approve / changes requested)
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Reviewer - Code Quality — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

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

@@ -47,3 +47,32 @@ Return a summary covering:
 - Code coverage improvements
 - Test run results (pass/fail counts)
 - Any production bugs discovered and fixed
+
+## Standalone Tracking
+
+When you are called directly by the user (NOT through an orchestrator — check: your prompt does NOT start with "This phase must be performed as the agent"), after completing your work:
+
+1. Read `docs/tracker-log.md` to see existing entries.
+2. Append a structured entry using this format:
+
+```markdown
+## Standalone: Unit Tester - Test Coverage — {Brief Task Description}
+
+**Date:** {YYYY-MM-DD}
+**Status:** ✅ SUCCESS | ⚠️ SKIPPED | ❌ FAILED
+
+### Summary
+{2-3 sentence plain-English summary of what was accomplished}
+
+### Files Produced / Modified
+| File | Description |
+
+### Key Decisions
+- {Decision and rationale}
+
+### Notes / Follow-up
+{Any caveats, open questions, or recommended next actions. "None" if nothing outstanding.}
+```
+
+3. Never overwrite existing content — only append.
+4. If called via orchestrator (prompt starts with "This phase must be performed as the agent"), do NOT write to `docs/tracker-log.md` — the orchestrator handles documentation.

package/package.json

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