goga-define

goga-define

Purpose

Orchestrate the product definition workflow and generate a complete PRD.

The orchestrator owns the workflow, not the product decisions.

It must keep the execution linear, delegate product work to specialized subskills, maintain the shared product context within the current agent session, detect conflicts, invoke the resolver when necessary, and finally generate the PRD.

---

Core Principle

The orchestrator is intentionally thin.

It must not perform product analysis itself when a specialized subskill exists for the task.

Its responsibilities are:

1. initialize the product context;
2. create and execute the workflow;
3. pass the required context to each subskill;
4. collect produced decisions;
5. detect conflicts;
6. invoke goga-define-resolve when conflicts occur;
7. update the shared context after resolution;
8. continue the linear pipeline;
9. generate the final PRD;
10. save it to the required location.

---

Shared Context

Maintain the product definition as an in-session context.

Do not create a separate database, persistent state store, or external context file.

Use a simple structure:

context:
  product: null
  input: null
  problem: null
  users: null
  goals: null
  user_experience: null
  requirements: null
  constraints: null
  scope: null
  success_criteria: null
  conflicts: []

This context is the source of truth for the current execution.

Subskills consume values from this context and produce new values.

Do not add IDs, metadata, timestamps, references, or other information that is not required for product reasoning.

---

Subskill Contracts

Each subskill declares what it consumes and produces.

Example:

consume:
  - product
  - problem
  - users

produce:
  - goals

The orchestrator must respect these contracts.

Do not pass arbitrary context when the subskill does not require it.

Do not ask a subskill to produce information outside its declared responsibility.

---

Workflow