@syntesseraai/opencode-feature-factory 0.6.17 → 0.6.19

package/command/pipeline/building/run.md

@@ -9,18 +9,3 @@ return:
   - /pipeline/building/implement-batch {as:build-implementation} $RESULT[build-batches]
   - /pipeline/reviewing/run {as:review-phase} $RESULT[build-implementation]
 ---
-
-Run build phase from the approved final plan passed in `$ARGUMENTS`.
-
-Rules:
-
-1. If `PLANNING_PROCEED=NO` appears in input, stop and return user-confirmation-required context instead of executing build tasks.
-2. Maintain dependency-safe batching.
-3. Only parallelize tasks with no dependency edges.
-4. Pass intermediate outputs via `{as:name}` and `$RESULT[name]`.
-5. Implementation is codex-focused via frontmatter model declaration in `implement-batch`.
-6. Send completed implementation output into reviewing via `/pipeline/reviewing/run`.
-
-Orchestrator constraint:
-
-This command is a **dispatch orchestrator only**. You must NOT directly read, edit, modify, write, or create any code files, configuration files, or repository files. Your sole responsibility is to invoke the declared sub-commands, pass structured data between them via `{as:name}` / `$RESULT[name]`, evaluate gate conditions, and route execution. All file-touching work belongs exclusively to the sub-commands (`breakdown`, `validate-batch`, `implement-batch`).

package/command/pipeline/documentation/run.md

@@ -12,20 +12,3 @@ return:
   - /pipeline/documentation/gate $RESULT[doc-review]
   - If `DOCUMENTATION_GATE=REWORK`, continue loop with review feedback for the next document pass.
 ---
-
-Execute the documentation stage for the current approved implementation.
-
-Orchestrator constraint:
-
-This command is a **dispatch orchestrator only**. You must NOT directly read, edit, modify, write, or create any code files, configuration files, or repository files. Your sole responsibility is to invoke the declared sub-commands (`document`, `review`, `gate`), pass structured data between them via `{as:name}` / `$RESULT[name]`, evaluate gate/loop conditions, and route execution. All file-touching work belongs exclusively to the leaf sub-commands.
-
-Skill requirements:
-
-1. ChatGPT supervisor must load `ff-todo-management` to track documentation actions and rework items per iteration.
-2. Documentation reviewer should use `ff-severity-classification` when reporting documentation issues.
-
-Stop criteria:
-
-- approve when documentation reviewer confirms documentation is complete, accurate, and repository docs are updated
-- continue loop while unresolved documentation issues exist and iteration < 5
-- escalate to user when iteration reaches 5 without approval

package/command/pipeline/planning/run.md

@@ -11,20 +11,3 @@ return:
   - /pipeline/planning/synthesize {as:plan-consensus} $RESULT[plan-opus] $RESULT[plan-gemini] $RESULT[plan-codex]
   - /pipeline/planning/gate $RESULT[plan-consensus]
 ---
-
-Run one complete planning iteration for the active pipeline.
-
-Orchestrator constraint:
-
-This command is a **dispatch orchestrator only**. You must NOT directly read, edit, modify, write, or create any code files, configuration files, or repository files. Your sole responsibility is to invoke the declared sub-commands (`plan`, `synthesize`, `gate`), pass structured data between them via `{as:name}` / `$RESULT[name]`, evaluate gate conditions, and route execution. All file-touching work belongs exclusively to the leaf sub-commands.
-
-Requirements brief:
-
-$ARGUMENTS
-
-Rules:
-
-1. Keep each planner output structured and concise for synthesis.
-2. Pass outputs using `{as:name}` and `$RESULT[name]` rather than intermediate files.
-3. Each planning model must include architecture validation in its proposal.
-4. Continue only through gate outcomes defined in `/pipeline/planning/gate`.

package/command/pipeline/reviewing/run.md

@@ -17,15 +17,3 @@ return:
   - /pipeline/reviewing/gate $RESULT[review-synthesis]
   - If `REVIEW_GATE=REWORK`, invoke `/pipeline/building/implement-batch` to apply fixes before the next loop iteration.
 ---
-
-Execute the review loop for the current completed tasks/rework report.
-
-Orchestrator constraint:
-
-This command is a **dispatch orchestrator only**. You must NOT directly read, edit, modify, write, or create any code files, configuration files, or repository files. Your sole responsibility is to invoke the declared sub-commands (`triage`, `review`, `synthesize`, `gate`, and rework dispatch), pass structured data between them via `{as:name}` / `$RESULT[name]`, evaluate gate/loop conditions, and route execution. All file-touching work belongs exclusively to the leaf sub-commands.
-
-Stop criteria:
-
-- approve when `>=95` confidence and zero unresolved issues
-- continue loop while unresolved issues exist and iteration < 10
-- escalate to user when iteration reaches 10 without approval

package/command/pipeline/start.md

@@ -4,26 +4,9 @@ subtask: true
 agent: general
 model: openai/gpt-5.4
 return:
-  - /pipeline/planning/run {as:planning-phase && loop:5 && until:planning gate is APPROVED or planning gate is BLOCKED and waiting for user confirmation}
+  - /pipeline/planning/run {as:planning-phase && loop:5 && until:planning gate is APPROVED or planning gate is BLOCKED and waiting for user confirmation} $ARGUMENTS
   - /pipeline/planning/confirm {as:planning-decision} $RESULT[planning-phase]
   - /pipeline/building/run {as:build-phase} $RESULT[planning-decision]
   - /pipeline/documentation/run $RESULT[build-phase]
   - /pipeline/complete
 ---
-
-Start the deterministic Feature Factory pipeline with this requirements brief:
-
-$ARGUMENTS
-
-Execution requirements:
-
-1. You are already inside `/pipeline/start`; do not invoke `/pipeline/start` again.
-2. Execute the declared return chain directly from this command.
-3. Use `{as:name}` and `$RESULT[name]` for phase-to-phase handoff.
-4. Avoid file persistence for intermediate artifacts unless a command explicitly requires audit snapshots.
-5. Use command chaining, parallel fan-out, and loop gates from the `/pipeline/...` command tree.
-6. Do not skip planning, review, and documentation gates.
-
-Orchestrator constraint:
-
-This command is a **top-level dispatch orchestrator only**. You must NOT directly read, edit, modify, write, or create any code files, configuration files, or repository files. Your sole responsibility is to invoke the declared phase commands in order, pass structured data between them via `{as:name}` / `$RESULT[name]`, and evaluate gate conditions. All file-touching work belongs exclusively to the leaf sub-commands within each phase.

package/package.json

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