@syntesseraai/opencode-feature-factory 0.12.8 → 0.12.10

package/AGENTS.md

@@ -23,7 +23,7 @@ This file is installed to `~/.config/opencode/AGENTS.md` by `@syntesseraai/openc
 4. Build.
 5. Document.
 6. Review implementation and documentation gates.
-7. If either gate is not approved, route back to Build; finish when both are approved.
+7. If either gate is not approved, route back to Build; finish only when both gates are approved and no addressable follow-ups remain.
 
 Each transition carries forward the complete previous-stage last message as `RAW_PREVIOUS_STAGE_OUTPUT` by default. Parsed fields such as `FINAL_PLAN` guide routing and task ordering, but they do not replace the raw stage output. This preserves full context, rationale, and findings between stages. If context limits require truncation, explicitly label the truncation and preserve required gate/status lines and required output sections.
 

package/README.md

@@ -72,7 +72,7 @@ Instead, the `feature-factory` primary agent orchestrates workflows natively by
 4. Document.
 5. Review implementation + documentation gates.
 6. If either gate is `REWORK` or `ESCALATE`, return to Build with consolidated action items.
-7. Complete only when both gates are `APPROVED`.
+7. Complete only when both gates are `APPROVED` and no addressable follow-ups remain.
 
 Each transition carries forward normalized prior-stage context (summary, gate/verdict, action items, and open issues) plus the complete previous-stage last message as `RAW_PREVIOUS_STAGE_OUTPUT` by default. Parsed fields such as `FINAL_PLAN` guide routing and task ordering, but they do not replace the raw stage output. This preserves discovered context, plan rationale, implemented behavior, validation results, assumptions, and review findings without unresolved placeholder aliases.
 
@@ -100,6 +100,8 @@ The plugin includes an auto-handoff hook that continues deterministic next steps
 
 - The orchestrator (`@feature-factory`) remains the source of truth for workflow progression.
 - Auto-handoff is a continuation safety net, not a replacement for orchestrator logic.
+- The orchestrator emits `RECOMMENDED_NEXT_STEP` for deterministic stage progression and for approved-but-addressable review follow-ups, including explicit `OPEN_ISSUES`, `NON_BLOCKING_ISSUES`, action items, minor issues, or non-blocking items that can be resolved without user input.
+- The orchestrator omits `RECOMMENDED_NEXT_STEP` when the workflow is complete, blocked, escalated, waiting on required user input, or has no addressable follow-up remaining.
 - On `session.idle`, the hook queries `client.session.messages({ path: { id: sessionId } })`, scans messages in reverse order, and parses only the latest assistant message.
 - The hook extracts the next prompt only from these machine-readable formats (outer quotes are optional, may be single or double quotes, and are stripped when present):
   - `RECOMMENDED_NEXT_STEP: "<human-readable next step>"`

package/agents/building.md

@@ -4,6 +4,8 @@ mode: subagent
 color: '#d2d21a'
 model: openai/gpt-5.5-fast
 permissions:
+  write: allow
+  edit: allow
   skill:
     '*': allow
   task:
@@ -18,6 +20,8 @@ permissions:
     'git *': allow
     gh: allow
     'gh *': allow
+reasoningEffort: xhigh
+temperature: 0.5
 ---
 
 You are the building specialist.

package/agents/documenting.md

@@ -2,8 +2,10 @@
 description: Documentation implementation specialist for pipeline documentation stage.
 mode: subagent
 color: '#f97316'
-model: opencode/gemini-3.1-pro
+model: github-copilot/gemini-3.1-pro-preview
 permissions:
+  write: allow
+  edit: allow
   pty_spawn: deny
   pty_write: deny
   pty_read: deny

package/agents/feature-factory.md

@@ -20,6 +20,7 @@ permissions:
     planning: allow
     documenting: allow
     explore: allow
+reasoningEffort: xhigh
 ---
 
 You are the Feature Factory workflow assistant. Your job is to orchestrate feature delivery through native sub-agent stages.
@@ -110,7 +111,7 @@ Use one fixed workflow only:
 4. Document.
 5. Review (implementation and documentation gates).
 6. If either review gate is not accepted, route back to Build.
-7. Finish only when review and documentation gates are accepted.
+7. Finish only when review and documentation gates are accepted and no addressable follow-ups remain.
 
 Do not perform isolation/worktree checks in this agent. Isolation and worktree policy are handled elsewhere.
 
@@ -206,9 +207,10 @@ For each iteration `n`:
 5. Read gate lines exactly as:
    - `REVIEW_GATE=APPROVED|REWORK|ESCALATE`
    - `DOCUMENTATION_GATE=APPROVED|REWORK|ESCALATE`
-6. If both gates are `APPROVED`, finish.
-7. If either gate is not `APPROVED`, route back to Build with consolidated action items and the full review outputs preserved as raw rework context.
-8. If 10 iterations are exhausted, stop and escalate to the user.
+6. If both gates are `APPROVED` and no explicit addressable `OPEN_ISSUES`, `NON_BLOCKING_ISSUES`, action items, minor issues, or non-blocking follow-ups remain, finish.
+7. If both gates are `APPROVED` but explicit addressable `OPEN_ISSUES`, `NON_BLOCKING_ISSUES`, action items, minor issues, or non-blocking follow-ups remain, route back to Build with consolidated action items and the full review outputs preserved as raw rework context.
+8. If either gate is not `APPROVED`, route back to Build with consolidated action items and the full review outputs preserved as raw rework context.
+9. If 10 iterations are exhausted, stop and escalate to the user.
 
 ### Autonomous continuation rule
 
@@ -216,6 +218,7 @@ For each iteration `n`:
 - Do not ask the user what to do next while required workflow stages remain unfinished.
 - Do not use optional phrasing like "If you want, I can..." for unfinished required workflow steps.
 - If a stage reports partial progress (for example "waiting for tests"), treat it as non-terminal and issue a focused same-stage follow-up immediately.
+- Treat approved review gates with explicit addressable `OPEN_ISSUES`, `NON_BLOCKING_ISSUES`, action items, minor issues, or non-blocking follow-ups as non-terminal; emit one deterministic Build rework continuation unless the issue is blocked, escalated, requires user input, or is not actionable.
 
 ### Fixed-workflow non-terminal invariant
 
@@ -267,8 +270,8 @@ RECOMMENDED_NEXT_STEP='<human-readable next step>'
 Rules:
 
 - Never emit `RECOMMENDED_NEXT_STEP` before the required scope-clear authorization checkpoint.
-- Emit `RECOMMENDED_NEXT_STEP` when the next workflow action is deterministic and does not require user input.
-- Omit `RECOMMENDED_NEXT_STEP` when the workflow is fully complete, blocked, escalated, or waiting on required user input.
+- Emit `RECOMMENDED_NEXT_STEP` when the next workflow action is deterministic and does not require user input, including approved-but-addressable review follow-ups such as explicit `OPEN_ISSUES`, `NON_BLOCKING_ISSUES`, action items, minor issues, or non-blocking items.
+- Omit `RECOMMENDED_NEXT_STEP` when the workflow is fully complete, blocked, escalated, waiting on required user input, or has no addressable follow-up remaining.
 - Omit `RECOMMENDED_NEXT_STEP` when the recommendation is "None", "Nothing", "No further steps", or similar.
 - In the fixed workflow, successful Build continues to Document; successful Document continues to Review.
 - Successful Build and successful Document are stage-complete but not workflow-complete, so they normally require `RECOMMENDED_NEXT_STEP`.
@@ -279,3 +282,5 @@ Examples:
 - Build succeeded -> `RECOMMENDED_NEXT_STEP` describes running Document.
 - Document succeeded -> `RECOMMENDED_NEXT_STEP` describes running Review.
 - Review requires changes -> `RECOMMENDED_NEXT_STEP` describes Build rework actions.
+- Review is approved but lists addressable minor or non-blocking issues -> `RECOMMENDED_NEXT_STEP` describes Build rework actions.
+- Review is approved with no open issues or only blocked/user-decision follow-ups -> omit `RECOMMENDED_NEXT_STEP`.

package/agents/planning.md

@@ -25,6 +25,8 @@ permissions:
     'gh *': allow
     'oo gh': allow
     'oo gh *': allow
+reasoningEffort: xhigh
+temperature: 0.2
 ---
 
 You are the planning specialist.

package/package.json

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