Skip to content

feat: Hybrid Discovery-Production Workflow#28

Merged
striderZA merged 2 commits intodevelopmentfrom
feat/hybrid-workflow
May 2, 2026
Merged

feat: Hybrid Discovery-Production Workflow#28
striderZA merged 2 commits intodevelopmentfrom
feat/hybrid-workflow

Conversation

@striderZA
Copy link
Copy Markdown
Owner

Summary

Introduces a hybrid workflow that splits the project lifecycle into two distinct modes: Discovery (pre-production) and Production, to better accommodate indie teams and creative iteration while preserving OCGS production discipline when it matters.

Motivation

The current OCGS framework requires 7+ formal stages before writing gameplay code. This is excellent for large teams with known designs, but creates excessive overhead for small indie teams still searching for the fun. This PR adds a first-class hybrid workflow that:

  • Reduces time-to-prototype from 2-4 weeks to 2-4 days
  • Lowers process overhead during early discovery
  • Maintains coordination quality once production begins

Changes

New Documentation

  • docs/hybrid-workflow.md — Complete two-phase model documentation:
    • Discovery Phase rules (no GDDs, no architecture, minimal agents)
    • Production Phase rules (full OCGS with consolidated 10-role hierarchy)
    • Decision gates (Prototype, Production, Alpha, Ship)
    • /prototype fast lane specification
    • Artifact comparison table
    • Migration path from hybrid to full OCGS

Updated Documentation

  • AGENTS.md — Added "Workflow Modes" section explaining Hybrid vs. Full OCGS, and added /prototype to the Getting Started command list

New Skill

  • .opencode/skills/hybrid-prototype/SKILL.md — Fast-lane prototype skill:
    • 6-phase flow: Concept → Plan → Build → Playtest → Decide → Done
    • Relaxed standards (hardcode freely, skip error handling)
    • No formal review gates (always fast)
    • Lightweight DECISION.md instead of formal REPORT.md
    • Comparison table showing differences from full /prototype skill

Acceptance Criteria

  • Hybrid workflow document written to docs/hybrid-workflow.md
  • AGENTS.md updated with discovery/production context
  • New /prototype skill created (as hybrid-prototype)
  • Slimmed agent hierarchy documented
  • Decision gates documented
  • No regression in existing production workflow

Testing

  • Verified no existing files were modified beyond AGENTS.md
  • Verified existing /prototype skill remains untouched
  • Verified new skill follows existing SKILL.md format conventions

Related Issue

Closes #27

- Add docs/hybrid-workflow.md: two-phase model, slimmed agent hierarchy,
  decision gates, and /prototype fast lane
- Update AGENTS.md with Workflow Modes section and /prototype command
- Add hybrid-prototype skill: 6-phase fast lane for discovery phase

Closes #27
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

I've reviewed all 3 changed files. Here's my analysis:


PR Review: feat: Hybrid Discovery-Production Workflow

Good

  • Well-structured document with clear two-phase model and decision gates
  • New skill follows existing SKILL.md format conventions (frontmatter, phases, constraints)
  • Strong isolation boundary: prototypes/ never imports from src/ and vice versa
  • Timeboxing and "kill cheaply" culture explicitly documented — good scope control
  • Migration path from hybrid → full OCGS is clearly defined

Issues

1. Misleading /prototype descriptionAGENTS.md:117

- `/prototype` — rapid prototype a concept (hybrid workflow)

The existing /prototype skill is the full OCGS prototype with 3 review modes (solo/lean/full), director gates, and formal REPORT.md. It is not a hybrid workflow command. The hybrid one is /hybrid-prototype. This label will confuse users into thinking /prototype follows relaxed rules, when it actually triggers the formal gate system.

2. Missing producer in the 10-role hierarchydocs/hybrid-workflow.md:68-81

Coordination Rule 4 in AGENTS.md states: "When a design change affects multiple domains, the producer agent coordinates the propagation." But the slimmed hierarchy drops producer with no replacement. Who handles cross-domain coordination in hybrid production mode?

3. /hybrid-prototype not listed in Available CommandsAGENTS.md:119-129

The new command is documented in the body text but absent from the command index. Users scanning for available commands won't find it.

4. .opencode/commands/ doesn't existAGENTS.md:24

The directory structure documents commands/ as the command location, but the directory doesn't exist — all commands live in .opencode/skills/. This is a pre-existing discrepancy that the PR could have cleaned up or noted. Newcomers will look for commands in the wrong directory.

5. No guard against review-mode bleedhybrid-prototype/SKILL.md

The full OCGS /prototype skill reads production/review-mode.txt to determine gate strictness. The hybrid skill doesn't, which is correct, but there's nothing preventing a session from accidentally inheriting stale review-mode state after switching workflows.


Suggestions

Severity Suggestion
High Fix AGENTS.md:117 — change description to "rapid prototype a concept" without "(hybrid workflow)"
Medium Assign producer duties to technical-director or creative-director in the slimmed hierarchy
Low Add /hybrid-prototype to the Available Commands list in AGENTS.md
Low Consider adding a note in the skill that it bypasses production/review-mode.txt entirely

Verdict: APPROVED with concerns. The design is sound and well-integrated, but the /prototype mislabeling will cause real confusion for users deciding which command to run.

New%20session%20-%202026-05-02T20%3A05%3A40.992Z
opencode session  |  github run

@striderZA striderZA merged commit 95cbaa7 into development May 2, 2026
1 check passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

Here's my review of the current state of the branch:

PR Review: feat: Hybrid Discovery-Production Workflow

What was fixed (since bot review #1)

  • /prototype description corrected — no longer says "(hybrid workflow)" ✅
  • /hybrid-prototype added to Available Commands (Prototyping category) ✅
  • Review-mode guard added to hybrid-prototype skill (line 137) ✅
  • Skill now references .opencode/docs/hybrid-workflow.md

Remaining issues

1. CRITICAL: Duplicate hybrid-workflow.md — stale copy diverged

Two copies exist:

  • docs/hybrid-workflow.mdcorrect (references /hybrid-prototype)
  • .opencode/docs/hybrid-workflow.mdstale (references /prototype in 2 places)

The .opencode/docs/ copy was added by fix commit #29 but wasn't updated with the corrected command name. It still says:

  • Line 115: ## The \/prototype` Fast Lane(should be/hybrid-prototype`)
  • Line 179: "The `/prototype` skill is designed to integrate cleanly..." (should be /hybrid-prototype)

Since the skill itself references .opencode/docs/hybrid-workflow.md, this stale copy will mislead anyone reading it. Pick one canonical location and remove the other.

2. MEDIUM: Coordination Rule 4 still references producer

AGENTS.md:50 — "When a design change affects multiple domains, the producer agent coordinates the propagation." The slimmed hierarchy drops producer (merged into technical-director). The hybrid workflow doc has a note explaining this, but AGENTS.md is the master config — a reader scanning it alone won't know who handles cross-domain coordination in hybrid mode.

Suggestions

Severity Suggestion
Critical Delete .opencode/docs/hybrid-workflow.md — it's stale and duplicates the canonical docs/hybrid-workflow.md
Medium Add a note in AGENTS.md Coordination Rule 4 that in hybrid mode, technical-director assumes producer duties
Low Remove the .opencode/docs/ reference in SKILL.md:13 if the canonical doc moves, or keep it consistent with whichever location survives

Verdict: APPROVED with changes. The design is solid. The stale duplicate file is the main blocker — it will cause confusion the moment someone reads the wrong copy.

New%20session%20-%202026-05-02T20%3A38%3A41.487Z
opencode session  |  github run

@striderZA striderZA deleted the feat/hybrid-workflow branch May 2, 2026 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant