@syntesseraai/opencode-feature-factory 0.11.0 → 0.11.2

package/AGENTS.md

@@ -12,8 +12,8 @@ This file is installed to `~/.config/opencode/AGENTS.md` by `@syntesseraai/openc
   - `reviewing` -> `opencode/glm-5.1`
   - `documenting` -> `opencode/gemini-3.1-pro`
 - Specialized agents: `feature-factory`, `planning`, `building`, `reviewing`, `documenting`, and `ff-research`.
-- Quick commands: `/ff-review [optional prompt]`, `/ff-document [optional prompt]`, and `/ff-rework [optional prompt]` (all run as subtasks on the relevant stage agent).
-- Skills for planning, documentation governance (`ff-documentation-rules`), review quality/security/architecture/documentation, GitHub workflows (`ff-github`), reporting templates, and todo management.
+- Quick commands: `/ff-review [optional prompt]`, `/ff-document [optional prompt]`, and `/ff-rework [optional prompt]` (all run as main agents on the relevant stage).
+- Skills for planning, command output compression (`ff-oo`), documentation governance (`ff-documentation-rules`), review quality/security/architecture/documentation, GitHub workflows (`ff-github`), reporting templates, and todo management.
 
 ## Preferred Workflow Pattern
 
@@ -41,8 +41,8 @@ When work changes behavior, workflows, configuration, operational guidance, or r
 - Use `read`, `glob`, and `grep` for targeted file inspection.
 - Writable agents should prefer `morph-mcp` `edit_file`, then fallback to native `edit` when needed.
 - Keep `edit` restricted on read-only agents (`planning`, `reviewing`, `ff-research`).
-- Route Git operations through `bash` with explicit `git`/`gh` allowlists (per OpenCode granular `permission.bash` rules, with last-match-wins ordering).
-- Keep read-only agents deny-first for shell usage (`bash: {'*': deny}` with explicit `git`/`gh` overrides).
+- Route Git operations through `bash` with explicit `git`/`gh` allowlists (and optional `oo git`/`oo gh` wrappers) per OpenCode granular `permission.bash` rules, with last-match-wins ordering.
+- Keep read-only agents deny-first for shell usage (`bash: {'*': deny}` with explicit `git`/`gh` and `oo git`/`oo gh` overrides).
 - Explicitly disable PTY tools (`pty_spawn`, `pty_write`, `pty_read`, `pty_list`, `pty_kill`) on read-only agents; they must not rely on PTY as a back door.
 - Use `todowrite` for multi-step tasks to keep progress visible.
 

package/README.md

@@ -2,7 +2,7 @@
 
 OpenCode plugin that provides Feature Factory agents, skills, commands, and native stage orchestration guidance.
 
-Notable bundled skills include `ff-mini-plan`, `ff-todo-management`, `ff-github` (GitHub CLI-first workflows with repo-local temp file guidance), and `ff-documentation-rules` (shared `docs/`, `INDEX.md`, and root `README.md` documentation governance).
+Notable bundled skills include `ff-mini-plan`, `ff-todo-management`, `ff-oo` (context-efficient shell command output compression with `oo` wrappers), `ff-github` (GitHub CLI-first workflows with repo-local temp file guidance), and `ff-documentation-rules` (shared `docs/`, `INDEX.md`, and root `README.md` documentation governance).
 
 ## Installation
 
@@ -82,8 +82,8 @@ Stage-agent code discovery is graph-first: planning/building/reviewing/documenti
 
 Feature Factory agent assets follow OpenCode granular permissions (`permission.bash`) with object syntax and deny/allow precedence based on **last matching rule wins**.
 
-- Stage agents (`planning`, `building`, `reviewing`, `documenting`, `ff-research`) expose `bash` and explicitly allow `git`/`gh` command patterns.
-- Read-only agents (`planning`, `reviewing`, `ff-research`) are deny-first for shell commands (`'*': deny`) with explicit `git`/`gh` exceptions.
+- Stage agents (`planning`, `building`, `reviewing`, `documenting`, `ff-research`) expose `bash` and explicitly allow `git`/`gh` command patterns, including `oo`-prefixed variants (`oo git ...`, `oo gh ...`).
+- Read-only agents (`planning`, `reviewing`, `ff-research`) are deny-first for shell commands (`'*': deny`) with explicit `git`/`gh` exceptions, including `oo git`/`oo gh`.
 - Read-only agents explicitly disable PTY tools (`pty_spawn`, `pty_write`, `pty_read`, `pty_list`, `pty_kill`) so command execution does not route through interactive PTY paths.
 
 ### Plugin auto-handoff safety net
@@ -101,17 +101,17 @@ The plugin installs global custom slash commands in `~/.config/opencode/commands
 
 - `/ff-review [optional prompt]`
   - Agent: `reviewing`
-  - Subtask: `true` (always runs as a subtask)
+  - Subtask: `false` (runs as a main agent)
   - Mode: manual standalone helper (does not continue the full pipeline automatically)
   - Default prompt when no argument is provided: `Review the changes so far`
 - `/ff-document [optional prompt]`
   - Agent: `documenting`
-  - Subtask: `true` (always runs as a subtask)
+  - Subtask: `false` (runs as a main agent)
   - Mode: manual standalone helper (does not continue the full pipeline automatically)
   - Default prompt when no argument is provided: `Document all the changes so far`
 - `/ff-rework [optional prompt]`
   - Agent: `building`
-  - Subtask: `true` (always runs as a subtask)
+  - Subtask: `false` (runs as a main agent)
   - Mode: manual standalone helper (does not continue the full pipeline automatically)
   - Default prompt when no argument is provided: `apply the rework recommendations`
 

package/agents/building.md

@@ -9,11 +9,6 @@ tools:
   edit: true
   edit_file: true
   bash: true
-  pty_spawn: false
-  pty_write: false
-  pty_read: false
-  pty_list: false
-  pty_kill: false
   skill: true
   task: true
   'codebase-memory-mcp_search_graph': true
@@ -31,7 +26,9 @@ permission:
     ff-research: allow
     explore: allow
   bash:
-    '*': ask
+    '*': allow
+    oo: allow
+    'oo *': allow
     git: allow
     'git *': allow
     gh: allow
@@ -92,6 +89,14 @@ Search fallback order:
 4. `read` to inspect exact implementation details before editing.
 5. `grep` for exact symbol/literal checks when needed.
 
+## Command Output Compression
+
+Always load `ff-oo` before running bash commands.
+
+- Prefer `oo <command>` execution when available to keep outputs context-efficient.
+- For GitHub workflows, prefer `oo git ...` / `oo gh ...` when `oo` is installed.
+- If `oo` is unavailable in the environment, run commands directly without `oo`.
+
 ## GitHub Workflow Guidance
 
 When implementation work includes GitHub operations (issues, PRs, checks, comments, releases), load `ff-github` and follow it:

package/agents/documenting.md

@@ -30,6 +30,8 @@ permission:
     explore: allow
   bash:
     '*': ask
+    oo: allow
+    'oo *': allow
     git: allow
     'git *': allow
     gh: allow
@@ -96,6 +98,14 @@ Search fallback order:
 4. `read` to verify exact behavior before writing docs.
 5. `grep` for exact symbol/literal checks when needed.
 
+## Command Output Compression
+
+Always load `ff-oo` before running bash commands.
+
+- Prefer `oo <command>` execution when available to keep outputs context-efficient.
+- For GitHub workflows, prefer `oo git ...` / `oo gh ...` when `oo` is installed.
+- If `oo` is unavailable in the environment, run commands directly without `oo`.
+
 ## GitHub Workflow Guidance
 
 When documenting GitHub-related workflows, load `ff-github` and keep the docs aligned with it:

package/agents/feature-factory.md

@@ -52,6 +52,8 @@ For any substantive user request, prefer sub-agent execution over direct handlin
 - `@reviewing`: validate implementation and documentation gates.
 - `@ff-research`: resolve external dependency or standards uncertainty.
 
+For every delegated stage, include an instruction to load `ff-oo` before any shell usage.
+
 Never complete implementation, documentation, validation, or research work directly in this agent when a relevant sub-agent exists.
 
 ## GitHub Workflow Guidance
@@ -62,6 +64,13 @@ When workflow scope includes GitHub operations (issues, PRs, checks, comments, r
 - Avoid generic web fetch/scraping for GitHub workflow state when `gh` can provide the data.
 - Keep downloaded artifacts repo-local (prefer `./.tmp/`), never `/tmp`.
 
+## Command Output Compression Guidance
+
+Enforce `ff-oo` in stage handoffs for command-heavy work:
+
+- Prefer `oo`-prefixed shell commands when available.
+- If `oo` is unavailable in the runtime, stages should fall back to direct commands.
+
 ---
 
 ## Documentation Governance
@@ -198,6 +207,14 @@ For each iteration `n`:
 - 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.
 
+### Fixed-workflow non-terminal invariant
+
+- After the required user confirmation checkpoint, successful Build always proceeds to Document.
+- After the required user confirmation checkpoint, successful Document always proceeds to Review.
+- Build and Document are stage-complete states, not workflow-complete states.
+- Therefore, successful Build and successful Document must emit `AUTO_HANDOFF=YES`.
+- Successful termination with `AUTO_HANDOFF=NO` is allowed only when Review is approved with no further required work (or when blocked/escalated/waiting on required user input).
+
 ### Direct-execution prohibition
 
 - Do not substitute manual/orchestrator-only answers for work that should be performed by stage agents.
@@ -235,10 +252,21 @@ FF_PROMPT
 
 Rules:
 
-- Use `AUTO_HANDOFF=YES` only when the next step is deterministic and should run automatically.
+- After the required user confirmation checkpoint, use `AUTO_HANDOFF=YES` whenever the next workflow step is predetermined by the fixed workflow.
+- In the fixed workflow, successful Build must always continue to Document.
+- In the fixed workflow, successful Document must always continue to Review.
+- Successful Build and successful Document are stage-complete but not workflow-complete; they must not output `AUTO_HANDOFF=NO`.
 - Use `AUTO_HANDOFF_TARGET=feature-factory` when the workflow should continue across multiple stages.
 - Use stage targets (`building`, `documenting`, `reviewing`) only for focused one-stage follow-up.
 - Never use `AUTO_HANDOFF=YES` before the required user confirmation checkpoint.
-- If complete, blocked, escalated, or waiting on the user, output `AUTO_HANDOFF=NO`.
+- Use `AUTO_HANDOFF=NO` only when the workflow is fully complete, blocked, escalated, or waiting on required user input.
 - `RECOMMENDED_NEXT_STEP` must match the machine-readable handoff block semantically.
 - For normal workflow progression, continue by delegating to stage agents directly (`@building`, `@documenting`, `@reviewing`), not by invoking slash commands such as `/ff-review`, `/ff-document`, or `/ff-rework`.
+
+Expected mappings:
+
+- Planning approved + user confirmed -> `AUTO_HANDOFF=YES`, `AUTO_HANDOFF_TARGET=feature-factory`, `AUTO_HANDOFF_REASON=CONTINUE_WORKFLOW`
+- Build succeeded -> `AUTO_HANDOFF=YES`, `AUTO_HANDOFF_TARGET=feature-factory`, `AUTO_HANDOFF_REASON=DOCUMENT`
+- Document succeeded -> `AUTO_HANDOFF=YES`, `AUTO_HANDOFF_TARGET=feature-factory`, `AUTO_HANDOFF_REASON=REVIEW`
+- Review requires changes -> `AUTO_HANDOFF=YES`, `AUTO_HANDOFF_TARGET=feature-factory`, `AUTO_HANDOFF_REASON=REWORK`
+- Review approved with no further work -> `AUTO_HANDOFF=NO`

package/agents/ff-research.md

@@ -28,8 +28,12 @@ permission:
     '*': deny
     git: allow
     'git *': allow
+    'oo git': allow
+    'oo git *': allow
     gh: allow
     'gh *': allow
+    'oo gh': allow
+    'oo gh *': allow
 ---
 
 You are the research specialist.
@@ -83,6 +87,13 @@ Search fallback order for code understanding:
 4. `morph-mcp_github_codebase_search` for upstream/public GitHub internals when needed.
 5. `gh_grep_searchGitHub` for exact code pattern matching across public repos.
 
+## Command Output Compression
+
+Always load `ff-oo` whenever this stage uses shell commands.
+
+- Prefer `oo git ...` / `oo gh ...` when `oo` is available.
+- If `oo` is unavailable, use direct `git`/`gh` commands.
+
 ## GitHub Workflow Guidance
 
 When research scope includes operational GitHub workflows (issues, PRs, checks, comments, releases), load `ff-github` and apply its constraints:

package/agents/planning.md

@@ -31,8 +31,12 @@ permission:
     '*': deny
     git: allow
     'git *': allow
+    'oo git': allow
+    'oo git *': allow
     gh: allow
     'gh *': allow
+    'oo gh': allow
+    'oo gh *': allow
 ---
 
 You are the planning specialist.
@@ -73,6 +77,13 @@ Search fallback order:
 4. `read` to verify relevant source context.
 5. `grep` for exact symbol/literal checks when needed.
 
+## Command Output Compression
+
+Always load `ff-oo` whenever this stage uses shell commands.
+
+- Prefer `oo git ...` / `oo gh ...` when `oo` is available.
+- If `oo` is unavailable, use direct `git`/`gh` commands.
+
 ## GitHub Workflow Guidance
 
 When planned work includes GitHub operations (issues, PRs, checks, comments, releases), load `ff-github` and encode its constraints in the plan:

package/agents/reviewing.md

@@ -31,8 +31,12 @@ permission:
     '*': deny
     git: allow
     'git *': allow
+    'oo git': allow
+    'oo git *': allow
     gh: allow
     'gh *': allow
+    'oo gh': allow
+    'oo gh *': allow
 ---
 
 You are the unified reviewing specialist.
@@ -73,6 +77,13 @@ Search fallback order:
 4. `read` to verify concrete evidence and line references.
 5. `grep` for exact symbol/literal checks when needed.
 
+## Command Output Compression
+
+Always load `ff-oo` whenever this stage uses shell commands.
+
+- Prefer `oo git ...` / `oo gh ...` when `oo` is available.
+- If `oo` is unavailable, use direct `git`/`gh` commands.
+
 ## GitHub Workflow Guidance
 
 When review scope includes GitHub operations (issues, PRs, checks, comments, releases), load `ff-github` and validate compliance:
@@ -91,6 +102,7 @@ When review scope includes repository documentation or documentation-impacting b
 
 ## Skills to Load by Scope
 
+- `ff-oo`
 - `ff-documentation-rules`
 - `ff-reviewing-code-quality`
 - `ff-reviewing-security`

package/commands/ff-document.md

@@ -1,7 +1,7 @@
 ---
-description: Quick documentation subtask (defaults to "Document all the changes so far")
+description: Quick documentation helper (defaults to "Document all the changes so far")
 agent: documenting
-subtask: true
+subtask: false
 ---
 
 $ARGUMENTS

package/commands/ff-review.md

@@ -1,7 +1,7 @@
 ---
-description: Quick review subtask (defaults to "Review the changes so far")
+description: Quick review helper (defaults to "Review the changes so far")
 agent: reviewing
-subtask: true
+subtask: false
 ---
 
 $ARGUMENTS

package/commands/ff-rework.md

@@ -1,7 +1,7 @@
 ---
-description: Quick rework subtask (defaults to "apply the rework recommendations")
+description: Quick rework helper (defaults to "apply the rework recommendations")
 agent: building
-subtask: true
+subtask: false
 ---
 
 $ARGUMENTS

package/package.json

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

package/skills/ff-oo/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: ff-oo
+description: Context-efficient command output guidance for agents using oo wrappers and recall workflow.
+license: Apache-2.0
+compatibility: opencode
+metadata:
+  audience: agents
+  category: workflow
+---
+
+# oo Command Compression Skill
+
+Use this skill whenever a task runs shell commands and large command output could consume context.
+
+## Primary Rule
+
+- Prefer `oo <command>` when `oo` is available in the runtime.
+- If `oo` is not available, run the command normally.
+
+Examples:
+
+```bash
+oo npm test
+oo git status
+oo gh pr view 123
+```
+
+## Why
+
+`oo` wraps normal commands and compresses verbose output into high-signal summaries (pass/fail, key errors, concise status), which reduces context waste for coding agents.
+
+## Retrieval Workflow
+
+When `oo` indexes large output, query it with recall:
+
+```bash
+oo recall "<query>"
+```
+
+Useful follow-ups:
+
+- `oo recall "error"`
+- `oo recall "failed"`
+- `oo recall "warning"`
+
+Clear indexed output when appropriate:
+
+```bash
+oo forget
+```
+
+## Git/GitHub Usage
+
+- Prefer `oo git ...` and `oo gh ...` for Git/GitHub workflows when available.
+- Keep standard non-`oo` fallbacks (`git ...`, `gh ...`) for environments where `oo` is not installed.
+
+## Operational Notes
+
+- Unknown commands may pass through unchanged (small output) or be indexed for recall (large output).
+- For command-specific compression improvements, `oo learn <command> [args...]` can teach new patterns.
+- `oo init` can emit integration snippets for agent setup.