@syntesseraai/opencode-feature-factory 0.6.9 → 0.6.10

package/README.md

@@ -23,13 +23,13 @@ This installer deploys to `~/.config/opencode/`:
 
 - `agents/`
 - `skills/`
-- `commands/`
+- `command/`
 
 It also updates `~/.config/opencode/opencode.json` non-destructively by merging missing Feature Factory MCP entries and plugins without deleting existing user configuration.
 
 ## Install Behavior
 
-- **Always overwrites packaged assets**: installer unconditionally overwrites Feature Factory `agents`, `skills`, and `commands` on every install.
+- **Always overwrites packaged assets**: installer unconditionally overwrites Feature Factory `agents`, `skills`, and `command` files on every install.
 - **`opencode.json` is non-destructive**: existing keys/values are preserved; only missing required plugin/MCP entries are added.
 - **Global scope**: assets are installed to `~/.config/opencode/` and shared across projects.
 
@@ -37,8 +37,8 @@ It also updates `~/.config/opencode/opencode.json` non-destructively by merging
 
 - Use `@pipeline` as the start experience.
 - The `@pipeline` agent handles intake and launches `/pipeline/start`.
-- Orchestration is implemented by the command tree under `commands/pipeline/` using subtask2 primitives (`return`, `parallel`, `loop`).
-- Coordinator and synthesis model is ChatGPT 5.4.
+- Orchestration is implemented by the command tree under `command/pipeline/` using subtask2 primitives (`return`, `parallel`, `loop`).
+- Coordinator and synthesis model defaults to ChatGPT 5.4 and can be overridden at runtime via `/pipeline/start` input.
 
 ## Command Tree
 
@@ -49,23 +49,28 @@ It also updates `~/.config/opencode/opencode.json` non-destructively by merging
 - `/pipeline/documentation/run`, `/pipeline/documentation/document`, `/pipeline/documentation/review`, `/pipeline/documentation/gate`
 - `/pipeline/complete`
 
-## Model Split
+## Model Routing
 
-- Coordinator and synthesis: ChatGPT 5.4
-- Planning/reviewing fan-out uses inline subtask2 model overrides from `/pipeline/planning/run` and `/pipeline/reviewing/run`
+- Runtime role keys are resolved at pipeline intake (`/pipeline/start`) and reused via `$RESULT[...]` across stages.
+- Cross-model steps use Task-C style dynamic subtask dispatch (`run /subtask {model:$RESULT[...]} ...`) where model switching is required.
+- `COORDINATOR_MODEL` (default: `openai/gpt-5.4`)
+- `DEVELOPER_MODEL` (default: `openai/gpt-5.3-codex`)
+- `ARCHITECT_MODEL` (default: `opencode/gemini-3.1-pro`)
+- `REVIEWER_MODEL` (default: `anthropic/claude-opus-4-6`)
+- `DOCUMENTATION_REVIEWER_MODEL` (default: `opencode/gemini-3.1-pro`)
 - Pipeline stages pass intermediate artifacts with `{as:name}` and `$RESULT[name]` (minimal file persistence)
-- Planning (with architecture validation): Codex, Gemini, Opus
-- Implementation: Codex only
-- Review (with architecture validation): Codex, Gemini, and Opus
-- Rework path: `/pipeline/reviewing/run` re-enters implementation via `/pipeline/building/implement-batch` when gate status is `REWORK`
-- Documentation stage: Codex updates documentation, Gemini reviews docs, and ChatGPT 5.4 supervises a bounded loop until approved
-- Documentation stage skill usage: Codex loads `ff-todo-management`, `ff-mini-plan`; Gemini loads `ff-report-templates` and `ff-severity-classification`
+- Planning (with architecture validation): reviewer, architect, and developer role models
+- Implementation: developer role model
+- Review (with architecture validation): reviewer, architect, and developer role models
+- Rework path: `/pipeline/reviewing/run` re-enters implementation via dynamic subtask dispatch targeting `/pipeline/building/implement-batch` when gate status is `REWORK`
+- Documentation stage: developer role updates documentation, documentation reviewer role reviews docs, and coordinator role supervises a bounded loop until approved
+- Documentation stage skill usage: developer role loads `ff-todo-management`, `ff-mini-plan`; documentation reviewer role loads `ff-report-templates` and `ff-severity-classification`
 
 ## Quality Gates
 
 - Planning approval: `>=75%` consensus.
 - Review approval: `>=95%` confidence and zero unresolved issues.
-- Documentation approval: Gemini verdict `APPROVED` with zero unresolved documentation issues.
+- Documentation approval: documentation reviewer verdict `APPROVED` with zero unresolved documentation issues.
 - Planning loop confirmation: after 5 unsuccessful planning iterations, pipeline asks user whether to continue.
 
 ## Related Docs

package/agents/pipeline.md

@@ -26,12 +26,13 @@ You are the pipeline orchestrator.
 ## Responsibilities
 
 1. Gather and confirm requirements.
-2. Start `/pipeline/start` with a concise requirements brief.
-3. Report phase transitions and gate outcomes.
+2. Propose the standard role model defaults and ask the user to confirm or override them before execution.
+3. Start `/pipeline/start` using the confirmed `COORDINATOR_MODEL` for the command model override, plus the confirmed role model keys.
+4. Report phase transitions and gate outcomes.
 
 ## Guardrails
 
-- Keep orchestration in command files under `commands/pipeline/`.
+- Keep orchestration in command files under `command/pipeline/`.
 - Use result-based chaining (`{as:name}` and `$RESULT[name]`) for intermediate handoff.
 - Enforce planning/review/documentation gates and loop limits.
 
@@ -42,6 +43,14 @@ You are the pipeline orchestrator.
 - Acceptance criteria
 - Scope constraints
 
-On confirmation, run:
+Before execution, confirm this default model set (allow overrides):
 
-`/pipeline/start <requirements-brief>`
+- `COORDINATOR_MODEL=openai/gpt-5.4`
+- `DEVELOPER_MODEL=openai/gpt-5.3-codex`
+- `ARCHITECT_MODEL=opencode/gemini-3.1-pro`
+- `REVIEWER_MODEL=anthropic/claude-opus-4-6`
+- `DOCUMENTATION_REVIEWER_MODEL=opencode/gemini-3.1-pro`
+
+After model confirmation, run:
+
+`/pipeline/start {model:<CONFIRMED_COORDINATOR_MODEL>} <requirements-brief with COORDINATOR_MODEL=<CONFIRMED_COORDINATOR_MODEL> DEVELOPER_MODEL=<CONFIRMED_DEVELOPER_MODEL> ARCHITECT_MODEL=<CONFIRMED_ARCHITECT_MODEL> REVIEWER_MODEL=<CONFIRMED_REVIEWER_MODEL> DOCUMENTATION_REVIEWER_MODEL=<CONFIRMED_DOCUMENTATION_REVIEWER_MODEL>>`

package/bin/ff-deploy.js

@@ -3,7 +3,7 @@
 /**
  * Feature Factory Deployment Script
  *
- * Deploys skills, agents, and commands to the global OpenCode configuration directory.
+ * Deploys skills, agents, and command files to the global OpenCode configuration directory.
  * Run manually with: npx @syntesseraai/opencode-feature-factory
  */
 
@@ -18,13 +18,13 @@ const __dirname = dirname(__filename);
 const GLOBAL_CONFIG_DIR = join(homedir(), '.config', 'opencode');
 const SKILLS_DIR = join(GLOBAL_CONFIG_DIR, 'skills');
 const AGENTS_DIR = join(GLOBAL_CONFIG_DIR, 'agents');
-const COMMANDS_DIR = join(GLOBAL_CONFIG_DIR, 'commands');
+const COMMAND_DIR = join(GLOBAL_CONFIG_DIR, 'command');
 const GLOBAL_CONFIG_FILE = join(GLOBAL_CONFIG_DIR, 'opencode.json');
 
 const PACKAGE_ROOT = join(__dirname, '..');
 const SOURCE_SKILLS_DIR = join(PACKAGE_ROOT, 'skills');
 const SOURCE_AGENTS_DIR = join(PACKAGE_ROOT, 'agents');
-const SOURCE_COMMANDS_DIR = join(PACKAGE_ROOT, 'commands');
+const SOURCE_COMMAND_DIR = join(PACKAGE_ROOT, 'command');
 
 // Check if running in interactive mode (has TTY)
 const isInteractive = process.stdin.isTTY && process.stdout.isTTY;
@@ -292,7 +292,7 @@ async function deploy() {
     await ensureDir(GLOBAL_CONFIG_DIR);
     await ensureDir(SKILLS_DIR);
     await ensureDir(AGENTS_DIR);
-    await ensureDir(COMMANDS_DIR);
+    await ensureDir(COMMAND_DIR);
 
     // Get existing skills/agents for reporting
     const existingSkills = await getDirectoryNames(SKILLS_DIR);
@@ -333,12 +333,12 @@ async function deploy() {
       }
     }
 
-    // Deploy commands
+    // Deploy command files
     if (isInteractive) {
       console.log('\n⌨️  Deploying Commands...');
     }
-    await copyDir(SOURCE_COMMANDS_DIR, COMMANDS_DIR);
-    const commandsCount = await getMarkdownFileCount(SOURCE_COMMANDS_DIR);
+    await copyDir(SOURCE_COMMAND_DIR, COMMAND_DIR);
+    const commandsCount = await getMarkdownFileCount(SOURCE_COMMAND_DIR);
     if (isInteractive) {
       console.log(`  ✅ pipeline commands (${commandsCount} files) (overwritten)`);
     }

package/{commands → command}/pipeline/building/breakdown.md

@@ -2,7 +2,6 @@
 description: Break final plan into atomic tasks
 subtask: true
 agent: building
-model: anthropic/claude-opus-4-6
 ---
 
 Read the approved final plan from `$ARGUMENTS` and produce atomic tasks.

package/{commands → command}/pipeline/building/implement-batch.md

@@ -2,7 +2,6 @@
 description: Implement validated batches with Codex
 subtask: true
 agent: building
-model: openai/gpt-5.3-codex
 ---
 
 Read `BATCHES` input from `$ARGUMENTS` and implement tasks batch-by-batch.

package/command/pipeline/building/run.md

@@ -0,0 +1,19 @@
+---
+description: Run build phase from approved plan
+subtask: true
+return:
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<REVIEWER_MODEL> && as:build-tasks} /pipeline/building/breakdown $ARGUMENTS'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<ARCHITECT_MODEL> && as:build-batches} /pipeline/building/validate-batch $RESULT[build-tasks]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<DEVELOPER_MODEL> && as:build-implementation} /pipeline/building/implement-batch $RESULT[build-batches]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/reviewing/run {model:<COORDINATOR_MODEL> && as:review-phase} $RESULT[build-implementation] COORDINATOR_MODEL=<COORDINATOR_MODEL> DEVELOPER_MODEL=<DEVELOPER_MODEL> ARCHITECT_MODEL=<ARCHITECT_MODEL> REVIEWER_MODEL=<REVIEWER_MODEL> DOCUMENTATION_REVIEWER_MODEL=<DOCUMENTATION_REVIEWER_MODEL>'
+---
+
+Run build phase from the approved final plan passed in `$ARGUMENTS`.
+
+Rules:
+
+1. Maintain dependency-safe batching.
+2. Only parallelize tasks with no dependency edges.
+3. Pass intermediate outputs via `{as:name}` and `$RESULT[name]`.
+4. Implementation uses the runtime-selected `DEVELOPER_MODEL` via inline model override.
+5. Send completed implementation output into reviewing via `/pipeline/reviewing/run`.

package/{commands → command}/pipeline/building/validate-batch.md

@@ -2,7 +2,6 @@
 description: Validate task batches for architecture and dependencies
 subtask: true
 agent: building
-model: opencode/gemini-3.1-pro
 ---
 
 Read `TASKS` input from `$ARGUMENTS` and create dependency-safe batches.

package/{commands → command}/pipeline/complete.md

@@ -1,7 +1,6 @@
 ---
 description: Finalize pipeline run and summarize outcomes
 subtask: true
-model: openai/gpt-5.4
 ---
 
 Finalize the pipeline run.

package/{commands → command}/pipeline/documentation/document.md

@@ -2,7 +2,6 @@
 description: Documentation write/update pass
 subtask: true
 agent: documenting
-model: openai/gpt-5.3-codex
 ---
 
 Document the approved code changes and update repository documentation.
@@ -16,7 +15,7 @@ Requirements:
 
 1. Use the latest approved review outputs and implementation artifacts as source of truth.
 2. Update all affected docs so behavior and operational steps match shipped code.
-3. If this is a rework iteration, incorporate Gemini feedback from the previous documentation review.
+3. If this is a rework iteration, incorporate documentation reviewer feedback from the previous documentation review.
 4. Summarize what docs were changed and why.
 
 Return a structured documentation update summary (no file persistence).

package/{commands → command}/pipeline/documentation/gate.md

@@ -1,7 +1,6 @@
 ---
 description: Apply documentation approval gate
 subtask: true
-model: openai/gpt-5.4
 ---
 
 Read the latest documentation review input from `$ARGUMENTS` and apply gate exactly:

package/{commands → command}/pipeline/documentation/review.md

@@ -2,7 +2,6 @@
 description: Documentation review pass
 subtask: true
 agent: reviewing
-model: opencode/gemini-3.1-pro
 ---
 
 Review the latest Codex documentation pass for completeness, correctness, and repository doc consistency.

package/command/pipeline/documentation/run.md

@@ -0,0 +1,25 @@
+---
+description: Run documentation loop after review approval
+subtask: true
+loop:
+  max: 5
+  until: documentation updates are approved by DOCUMENTATION_REVIEWER_MODEL with zero unresolved documentation issues
+return:
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<DEVELOPER_MODEL> && as:doc-pass} /pipeline/documentation/document $ARGUMENTS'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<DOCUMENTATION_REVIEWER_MODEL> && as:doc-review} /pipeline/documentation/review $RESULT[doc-pass]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/documentation/gate {model:<COORDINATOR_MODEL>} $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.
+
+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/{commands → command}/pipeline/planning/gate.md

@@ -2,7 +2,6 @@
 description: Apply planning consensus gate
 subtask: true
 agent: planning
-model: openai/gpt-5.4
 ---
 
 Apply the planning gate to the synthesized consensus input passed in `$ARGUMENTS`:

package/command/pipeline/planning/run.md

@@ -0,0 +1,24 @@
+---
+description: Execute one planning iteration
+subtask: true
+parallel:
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<REVIEWER_MODEL> && as:plan-reviewer} /pipeline/planning/plan [MODEL_TAG:reviewer] $ARGUMENTS'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<ARCHITECT_MODEL> && as:plan-architect} /pipeline/planning/plan [MODEL_TAG:architect] $ARGUMENTS'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<DEVELOPER_MODEL> && as:plan-developer} /pipeline/planning/plan [MODEL_TAG:developer] $ARGUMENTS'
+return:
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/planning/synthesize {model:<COORDINATOR_MODEL> && as:plan-consensus} $RESULT[plan-reviewer] $RESULT[plan-architect] $RESULT[plan-developer]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/planning/gate {model:<COORDINATOR_MODEL>} $RESULT[plan-consensus]'
+---
+
+Run one complete planning iteration for the active pipeline.
+
+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/{commands → command}/pipeline/planning/synthesize.md

@@ -2,14 +2,13 @@
 description: Synthesize planning consensus
 subtask: true
 agent: planning
-model: openai/gpt-5.4
 ---
 
 Synthesize the three model outputs from planning fan-out:
 
-- `$RESULT[plan-opus]`
-- `$RESULT[plan-gemini]`
-- `$RESULT[plan-codex]`
+- `$RESULT[plan-reviewer]`
+- `$RESULT[plan-architect]`
+- `$RESULT[plan-developer]`
 
 Produce a consensus report (no file persistence).
 

package/{commands → command}/pipeline/reviewing/gate.md

@@ -2,7 +2,6 @@
 description: Apply review approval gate
 subtask: true
 agent: reviewing
-model: openai/gpt-5.4
 ---
 
 Read the synthesized review input from `$ARGUMENTS` and apply gate exactly:

package/command/pipeline/reviewing/run.md

@@ -0,0 +1,23 @@
+---
+description: Run review loop for completed tasks
+subtask: true
+loop:
+  max: 10
+  until: all tasks in the active batch are approved with confidence >=95 and zero unresolved issues
+return:
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/reviewing/triage {model:<COORDINATOR_MODEL> && as:review-brief} $ARGUMENTS'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<REVIEWER_MODEL> && as:review-reviewer} /pipeline/reviewing/review [MODEL_TAG:reviewer] $RESULT[review-brief]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<ARCHITECT_MODEL> && as:review-architect} /pipeline/reviewing/review [MODEL_TAG:architect] $RESULT[review-brief]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<DEVELOPER_MODEL> && as:review-developer} /pipeline/reviewing/review [MODEL_TAG:developer] $RESULT[review-brief]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/reviewing/synthesize {model:<COORDINATOR_MODEL> && as:review-synthesis} $RESULT[review-reviewer] $RESULT[review-architect] $RESULT[review-developer]'
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/reviewing/gate {model:<COORDINATOR_MODEL>} $RESULT[review-synthesis]'
+  - If REVIEW_GATE=REWORK, run, replacing arguments with values from $ARGUMENTS: /subtask {agent:general && model:<DEVELOPER_MODEL>} /pipeline/building/implement-batch $RESULT[review-synthesis]
+---
+
+Execute the review loop for the current completed tasks/rework report.
+
+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/{commands → command}/pipeline/reviewing/synthesize.md

@@ -2,10 +2,9 @@
 description: Synthesize independent reviews into one report
 subtask: true
 agent: reviewing
-model: openai/gpt-5.4
 ---
 
-Read the three review inputs passed in `$ARGUMENTS` (Opus, Gemini, Codex) and synthesize a single authoritative output.
+Read the three review inputs passed in `$ARGUMENTS` (reviewer, architect, developer) and synthesize a single authoritative output.
 
 Required output:
 

package/{commands → command}/pipeline/reviewing/triage.md

@@ -2,7 +2,6 @@
 description: Build review brief from implementation outputs
 subtask: true
 agent: reviewing
-model: openai/gpt-5.4
 ---
 
 Prepare a review brief for the current completed task or rework output.

package/command/pipeline/start.md

@@ -0,0 +1,29 @@
+---
+description: Pipeline workflow entrypoint
+subtask: true
+return:
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/planning/run {model:<COORDINATOR_MODEL> && as:planning-phase && loop:5 && until:planning gate is APPROVED or planning gate is BLOCKED and waiting for user confirmation} $ARGUMENTS'
+  - If planning is BLOCKED or loop max was reached, stop and ask the user whether to continue planning iterations. Otherwise continue.
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/building/run {model:<COORDINATOR_MODEL> && as:build-phase} $RESULT[planning-phase] COORDINATOR_MODEL=<COORDINATOR_MODEL> DEVELOPER_MODEL=<DEVELOPER_MODEL> ARCHITECT_MODEL=<ARCHITECT_MODEL> REVIEWER_MODEL=<REVIEWER_MODEL> DOCUMENTATION_REVIEWER_MODEL=<DOCUMENTATION_REVIEWER_MODEL>'
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/documentation/run {model:<COORDINATOR_MODEL>} $RESULT[build-phase] COORDINATOR_MODEL=<COORDINATOR_MODEL> DEVELOPER_MODEL=<DEVELOPER_MODEL> ARCHITECT_MODEL=<ARCHITECT_MODEL> REVIEWER_MODEL=<REVIEWER_MODEL> DOCUMENTATION_REVIEWER_MODEL=<DOCUMENTATION_REVIEWER_MODEL>'
+  - 'run, replacing arguments with values from $ARGUMENTS: /pipeline/complete {model:<COORDINATOR_MODEL>}'
+---
+
+Start the deterministic Feature Factory pipeline with this requirements brief:
+
+$ARGUMENTS
+
+Optional runtime model inputs (recommended):
+
+- `COORDINATOR_MODEL=<provider/model>`
+- `DEVELOPER_MODEL=<provider/model>`
+- `ARCHITECT_MODEL=<provider/model>`
+- `REVIEWER_MODEL=<provider/model>`
+- `DOCUMENTATION_REVIEWER_MODEL=<provider/model>`
+
+Execution requirements:
+
+1. Use `{as:name}` and `$RESULT[name]` for phase-to-phase handoff.
+2. Avoid file persistence for intermediate artifacts unless a command explicitly requires audit snapshots.
+3. Use command chaining, parallel fan-out, and loop gates from the `/pipeline/...` command tree.
+4. Do not skip planning, review, and documentation gates.

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "@syntesseraai/opencode-feature-factory",
-  "version": "0.6.9",
+  "version": "0.6.10",
   "type": "module",
   "description": "OpenCode plugin for Feature Factory agents - provides sub-agents and skills for validation, review, security, and architecture assessment",
   "license": "MIT",
@@ -15,7 +15,7 @@
     "assets",
     "skills",
     "agents",
-    "commands",
+    "command",
     "bin"
   ],
   "keywords": [

package/commands/pipeline/building/run.md

@@ -1,19 +0,0 @@
----
-description: Run build phase from approved plan
-subtask: true
-return:
-  - /pipeline/building/breakdown {as:build-tasks} $ARGUMENTS
-  - /pipeline/building/validate-batch {as:build-batches} $RESULT[build-tasks]
-  - /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. Maintain dependency-safe batching.
-2. Only parallelize tasks with no dependency edges.
-3. Pass intermediate outputs via `{as:name}` and `$RESULT[name]`.
-4. Implementation is Codex-only via `building` with model `openai/gpt-5.3-codex`.
-5. Send completed implementation output into reviewing via `/pipeline/reviewing/run`.

package/commands/pipeline/documentation/run.md

@@ -1,26 +0,0 @@
----
-description: Run documentation loop after review approval
-subtask: true
-model: openai/gpt-5.4
-loop:
-  max: 5
-  until: documentation updates are approved by Gemini with zero unresolved documentation issues
-return:
-  - /pipeline/documentation/document {as:doc-pass} $ARGUMENTS
-  - /pipeline/documentation/review {as:doc-review} $RESULT[doc-pass]
-  - /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.
-
-Skill requirements:
-
-1. ChatGPT supervisor must load `ff-todo-management` to track documentation actions and rework items per iteration.
-2. Gemini reviewer should use `ff-severity-classification` when reporting documentation issues.
-
-Stop criteria:
-
-- approve when Gemini 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/commands/pipeline/planning/run.md

@@ -1,25 +0,0 @@
----
-description: Execute one planning iteration
-subtask: true
-model: openai/gpt-5.4
-parallel:
-  - /pipeline/planning/plan {model:anthropic/claude-opus-4-6 && as:plan-opus} [MODEL_TAG:opus] $ARGUMENTS
-  - /pipeline/planning/plan {model:opencode/gemini-3.1-pro && as:plan-gemini} [MODEL_TAG:gemini] $ARGUMENTS
-  - /pipeline/planning/plan {model:openai/gpt-5.3-codex && as:plan-codex} [MODEL_TAG:codex] $ARGUMENTS
-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.
-
-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/commands/pipeline/reviewing/run.md

@@ -1,24 +0,0 @@
----
-description: Run review loop for completed tasks
-subtask: true
-model: openai/gpt-5.4
-loop:
-  max: 10
-  until: all tasks in the active batch are approved with confidence >=95 and zero unresolved issues
-return:
-  - /pipeline/reviewing/triage {as:review-brief} $ARGUMENTS
-  - /pipeline/reviewing/review {model:anthropic/claude-opus-4-6 && as:review-opus} [MODEL_TAG:opus] $RESULT[review-brief]
-  - /pipeline/reviewing/review {model:opencode/gemini-3.1-pro && as:review-gemini} [MODEL_TAG:gemini] $RESULT[review-brief]
-  - /pipeline/reviewing/review {model:openai/gpt-5.3-codex && as:review-codex} [MODEL_TAG:codex] $RESULT[review-brief]
-  - /pipeline/reviewing/synthesize {as:review-synthesis} $RESULT[review-opus] $RESULT[review-gemini] $RESULT[review-codex]
-  - /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.
-
-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/commands/pipeline/start.md

@@ -1,22 +0,0 @@
----
-description: Pipeline workflow entrypoint
-subtask: true
-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}
-  - If planning is BLOCKED or loop max was reached, stop and ask the user whether to continue planning iterations. Otherwise continue.
-  - /pipeline/building/run {as:build-phase} $RESULT[planning-phase]
-  - /pipeline/documentation/run $RESULT[build-phase]
-  - /pipeline/complete
----
-
-Start the deterministic Feature Factory pipeline with this requirements brief:
-
-$ARGUMENTS
-
-Execution requirements:
-
-1. Use `{as:name}` and `$RESULT[name]` for phase-to-phase handoff.
-2. Avoid file persistence for intermediate artifacts unless a command explicitly requires audit snapshots.
-3. Use command chaining, parallel fan-out, and loop gates from the `/pipeline/...` command tree.
-4. Do not skip planning, review, and documentation gates.