# Goga Brainstorm Plan Assembly

> Assembly of the architecture plan document

- Skill: `qarium/goga-brainstorm-plan-assembly` (Agent Skill)
- Install (CLI): `npx skillmds@latest add qarium/goga-brainstorm-plan-assembly`
- Raw SKILL.md: https://api.skillmd.com/api/skills/qarium/goga-brainstorm-plan-assembly/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: qarium (https://skillmd.com/u/qarium)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/qarium/goga-brainstorm-plan-assembly

---


# goga-brainstorm-plan-assembly

## Identity

You are responsible for assembling the architecture plan — a structured document describing CODEMANIFEST and `.usages/`
files for each cell — and writing it to disk.

## Context

Use these reports for its specific purpose:

- **`[CELL_ASSEMBLY_REPORT]`** — use it for the assembled per-cell **CODEMANIFESTs and `.usages/` files**, the
  **dependency diagram**, and the **artifact list** — the material to write into the plan.
- **`[PRIMARY_ANALYSIS_REPORT]`** — use its **Topic** as the plan's short name, its **Existing Cells & Schema** for the
  project structure (file names and paths), and its **Artifact Resolution** to mark each cell as modified vs created
  anew.

## Workflow

### Phase 1. Determine the topic

Resolve the topic directory — the path printed by `goga history path` (the current topic in the history tree).
Keep the **Topic** section of the `[PRIMARY_ANALYSIS_REPORT]` as the plan's short name.

### Phase 2. Assemble the plan structure

Build the plan with the following sections.

#### Implementation order

Cells ordered from leaves to root (cells without dependencies first, then dependent ones). For each cell, specify the
reason for the order (e.g., "has no Imports", "depends on cell X").

#### Artifacts for each cell

For each cell in implementation order:

- **CODEMANIFEST** — complete file contents in DSL format
- **.usages/ files** — for each file: path, name, complete contents

#### Dependency map

ASCII diagram or list of connections between cells via Imports.

#### Verification checklist

What to check after implementing each artifact.

### Phase 3. Apply plan generation rules

- Each CODEMANIFEST in the plan must be syntactically correct per the DSL specification
- File names and paths must correspond to the project structure from the Existing Cells & Schema section of the
  `[PRIMARY_ANALYSIS_REPORT]`
- For modification of existing CODEMANIFESTs — specify a diff: what to add, change, delete
- Explicitly mark which cells are modified vs created anew (per the Artifact Resolution in the
  `[PRIMARY_ANALYSIS_REPORT]`)
- The plan contains ONLY CODEMANIFEST and `.usages/` file artifacts — no implementation code in any language

### Phase 4. Save the plan

Save the plan to the path printed by `goga history path -f arch.md`
(run `goga history ensure` first if the topic directory does not exist).

## WAIT

Present the plan to the user and obtain confirmation.

## Output Format

Fill every section. No empty sections.

```md
# [ARCHITECTURE_PLAN]

## Topic
[Short name and the path printed by `goga history path -f arch.md`]

## Implementation Order
[Ordered list of cells, leaves to root, with rationale per cell]

## Artifacts
[For each cell: CODEMANIFEST (full DSL) + .usages/ files (full content). For existing cells: diff.]

## Dependency Map
[ASCII diagram or list of inter-cell Imports connections]

## Verification Checklist
[What to check after implementing each artifact]
```

## STOP if:
- plan incomplete (missing section, missing cell, placeholder content)