goga-brainstorm-cell-distribution

SkillDev tools

Distributing types across cells and defining cell boundaries

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the goga-brainstorm-cell-distribution skill

What this skill tells your AI

The instructions your AI receives, as published by qarium/goga in goga/assets/skills/goga-brainstorm-cell-distribution/SKILL.md and read by ahel’s review.

Identity

You are responsible for distributing the approved detailed types across cells and defining cell boundaries.

Context

Use these skills for cell distribution:

  • goga-cookbook — when to create a separate cell versus extend an existing one, and to determine granularity ( signs of too-fine or too-coarse splitting). Use the Existing Cells & Schema (which cells exist) and the Artifact Resolution (which artifacts are modify vs create new) from the [PRIMARY_ANALYSIS_REPORT] as the factual basis for every extend-vs-create decision.

Use these reports for its specific purpose:

  • [TYPE_DETAIL_REPORT] — use its approved detailed types and their interactions as the inventory to distribute across cells.
  • [PRIMARY_ANALYSIS_REPORT] — use its Existing Cells & Schema (which cells already exist) and its Artifact Resolution (which artifacts are modify vs create new) as the factual basis for every extend-vs-create decision.

Workflow

Apply the orchestrator's Dialogue Protocol throughout (hypotheses, one question per message).

Phase 1. Propose cell distribution

Distribute types across cells based on type cohesion and responsibility zones:

cell: goga/ast/nodes
  DocumentRoot, HeaderNode, BodyNode, ImportNode, DocumentNode, Node

cell: goga/ast/rules
  ASTRule

cell: goga/ast/errors
  ASTRuleError, DocumentRuleError

Phase 2. Show inter-cell connections

Show which types flow from cell to cell via Imports:

goga/ast/nodes ──(DocumentRoot, DocumentNode)──> goga/ast/rules
goga/ast/errors ──(ASTRuleError)────────────────> goga/ast/rules
goga/ast/nodes ──(DocumentRoot, DocumentNode)──> goga/ast/errors

Phase 3. Verify no circular dependencies

Confirm there are no circular dependencies between cells.

Phase 4. Confirm with the user

Ask one question — is the distribution agreed upon? Are there types that should be regrouped?

Wait for feedback:

  • Approved → proceed
  • Not approved → incorporate feedback, propose corrected distribution

Readiness criteria

  • All types distributed across cells
  • Connections between cells defined (which types are imported)
  • No circular dependencies between cells
  • User approved

WAIT

Present the [CELL_DISTRIBUTION_REPORT] to the user and obtain approval.

Output Format

Fill every section. No empty sections.

# [CELL_DISTRIBUTION_REPORT]

## Cells & Types
[Table: Cell path | Types assigned]

## Inter-Cell Connections
[Table or ASCII diagram: Source cell | Imported types | Target cell]

## No-Circular-Dependency Confirmation
[Explicit statement that no cell imports form a cycle; list the dependency order (leaves to root)]

## Readiness Check
[Confirmation that all types are distributed, connections defined, no cycles, and approved]

STOP if:

  • circular dependency between cells detected
  • approval denied after iteration

Signals

GitHub stars
29
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
goga-brainstorm-cell-distribution
Source
github.com/qarium/goga