@syntesseraai/opencode-feature-factory

OpenCode plugin that provides Feature Factory agents, skills, and pipeline commands.

Installation

1) Add plugin to your project config

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@syntesseraai/opencode-feature-factory"]
}

2) Install global assets

npx @syntesseraai/opencode-feature-factory install

This installer deploys to ~/.config/opencode/:

• agents/
• skills/
• 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 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.

Pipeline Entrypoint

• Use @pipeline as the start experience.
• The @pipeline agent handles intake and launches /pipeline/start.
• 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

• /pipeline/start
• /pipeline/planning/run, /pipeline/planning/plan, /pipeline/planning/synthesize, /pipeline/planning/gate, /pipeline/planning/confirm
• /pipeline/building/run, /pipeline/building/breakdown, /pipeline/building/validate-batch, /pipeline/building/implement-batch
• /pipeline/reviewing/run, /pipeline/reviewing/triage, /pipeline/reviewing/review, /pipeline/reviewing/synthesize, /pipeline/reviewing/gate
• /pipeline/documentation/run, /pipeline/documentation/document, /pipeline/documentation/review, /pipeline/documentation/gate
• /pipeline/complete
• /mini-loop/start
• /mini-loop/implementation/run, /mini-loop/implementation/build, /mini-loop/implementation/review, /mini-loop/implementation/gate
• /mini-loop/documentation/run, /mini-loop/documentation/document, /mini-loop/documentation/review, /mini-loop/documentation/gate

Model Routing

• Coordinator and synthesis model is ChatGPT 5.4.
• Planning/reviewing fan-out uses explicit inline model overrides.
• DEVELOPER_MODEL: openai/gpt-5.3-codex
• ARCHITECT_MODEL: opencode/gemini-3.1-pro
• REVIEWER_MODEL: anthropic/claude-opus-4-6
• COORDINATOR_MODEL: openai/gpt-5.4
• DOCUMENTATION_REVIEWER_MODEL: opencode/gemini-3.1-pro
• Pipeline stages pass intermediate artifacts with {as:name} and $RESULT[name] (minimal file persistence)
• 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 /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: 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

• docs/PIPELINE_ORCHESTRATION.md
• docs/PLUGIN_PUBLISH.md

License

MIT