@syntesseraai/opencode-feature-factory 0.11.7 → 0.11.8

package/README.md

@@ -74,7 +74,7 @@ Instead, the `feature-factory` primary agent orchestrates workflows natively by
 6. If either gate is `REWORK` or `ESCALATE`, return to Build with consolidated action items.
 7. Complete only when both gates are `APPROVED`.
 
-Each transition carries forward prior-stage context (summary, gate/verdict, action items, open issues, and raw output via `$RESULT[...]`) so downstream stages receive full handoff state.
+Each transition carries forward normalized prior-stage context (summary, gate/verdict, action items, open issues, and resolved prior output excerpts sourced from previous stage output or existing context) so downstream stages receive full handoff state without unresolved placeholder aliases.
 
 Writable stage agents (`building`, `documenting`) prefer Morph MCP `edit_file` and can fallback to native `edit` (and `write` for new files) when needed. Read-only agents keep `edit` disabled.
 

package/agents/building.md

@@ -49,7 +49,8 @@ You are the building specialist.
 
 ## Operating Mode
 
-- Use plan/build/review command handoff via `$RESULT[...]`.
+- Use normalized, resolved stage handoff context from prior-stage output or existing context.
+- Never rely on unresolved placeholder aliases in handoff prompts.
 - Do not rely on intermediate artifact files for pipeline progression.
 - Persist only when explicitly requested by the user.
 

package/agents/documenting.md

@@ -52,6 +52,11 @@ You are the documenting specialist.
 - Explain what changed, why it matters, when a reader should use the document, and where they should go next.
 - Return a structured summary for documentation review.
 
+## Operating Mode
+
+- Use normalized, resolved stage handoff context from prior-stage output or existing context.
+- Never rely on unresolved placeholder aliases in handoff prompts.
+
 ## Shared Documentation Rules (Required)
 
 Always load `ff-documentation-rules` before scoping or editing documentation. Treat it as the authoritative rule set for repository documentation placement, `INDEX.md` navigation, cross-references, and root `README.md` entry points.

package/agents/feature-factory.md

@@ -130,7 +130,7 @@ When delegating each stage, include:
 3. **Previous stage summary**
 4. **Previous stage gate/verdict**
 5. **Key action items / issues**
-6. **Raw prior output via `$RESULT[...]`**
+6. **Resolved prior output context (never unresolved placeholders)**
 
 ### Handoff template (use for every transition)
 
@@ -148,12 +148,20 @@ PREVIOUS_STAGE_OPEN_ISSUES:
 - ...
 
 RAW_PREVIOUS_STAGE_OUTPUT:
-$RESULT[<previous_stage_alias>]
+<resolved prior-stage output excerpt or summary>
+
+RESOLUTION_SOURCE:
+<previous stage output | existing context>
+
+PLACEHOLDER_CHECK:
+PASS (no unresolved placeholder tokens such as unresolved result aliases)
 
 CURRENT_STAGE_OBJECTIVE:
 <what this stage must do now>
 ```
 
+Never pass unresolved placeholder aliases (for example unresolved result-alias syntax) in stage handoff prompts.
+
 ### "Clear and obvious" transition rule
 
 Move to the next stage only when output is clear and obvious, meaning:

package/agents/planning.md

@@ -110,7 +110,8 @@ For external/library uncertainty, use the shared `ff-research-methods` skill dir
 ## Operating Mode
 
 - Prefer deterministic, structured output sections.
-- Use result-based orchestration (`{as:name}` and `$RESULT[name]`) for handoff.
+- Use normalized, resolved handoff context in stage transitions (summary, status, action items, open issues, and resolved prior output excerpts).
+- Never rely on unresolved placeholder aliases in handoff prompts.
 - Avoid writing intermediate plan files unless a user explicitly requests durable artifacts.
 
 ## Required Output Sections

package/agents/reviewing.md

@@ -154,7 +154,8 @@ AUTO_HANDOFF=NO
 
 ## Operating Mode
 
-- Use result-based handoff (`$RESULT[...]`) rather than file-based artifacts.
+- Use normalized, resolved handoff context (summary/status/action items/issues plus resolved prior output excerpts) rather than file-based artifacts.
+- Never rely on unresolved placeholder aliases in handoff prompts.
 - Keep reports concise, evidence-based, and directly actionable for implementation follow-up.
 - Do not delegate to implementation stages from reviewing mode.
 - Never perform implementation or file-modifying work in reviewing mode.

package/package.json

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