Five plugins shipped — one shape

Most people using AI for creative and technical work eventually run into the same problem: the same session that helped them write a product brief is now being asked to review a line of TypeScript. The output degrades — not because the model is incapable, but because the context is contaminated.

The Great Minds Constellation is the architectural answer to that problem.

What the Constellation is

Eleven plugins. Each represents a distinct craft — prose, visual storytelling, packaging, distribution, engineering, design, operations, law, research, education, and orchestration. Each is independently installable, versioned, and replaceable. Together they form what you would staff if you were building a full creative company.

All eleven now ship in one marketplace at github.com/sethshoultes/great-minds-constellation. Five anchor the foundation — great-minds (orchestration), great-authors (prose), great-filmmakers (visual storytelling), great-publishers (packaging), and great-marketers (distribution). Six expansion plugins — covered in Module 3 — extend the set into engineering, design, operations, counsel, research, and education. The course preserves Module 3's original framing of these as "stars not yet lit" as a record of how the constellation grew; the plugins themselves are installable today.

What every shipped plugin shares

Walk into any of the five plugins and you will find the same skeleton. A persona file written in the craft's own register. A decision table mapping signals to personas — when is this a Hemingway problem versus a Baldwin problem? A pipeline that moves from discovery to debate to plan to build to QA to review.

The skeleton is not an accident. It is the interface. When you know where to find the persona file in great-authors, you know where to find it in great-filmmakers. The pattern is load-bearing.

The concrete shape

Open .great-authors/hemingway-persona.md and you will not find a biography. You will find: cut adverbs, trust the noun, what is left out carries the weight. That is a register document, not a job description. The model reads it, adopts it, and stays in it.

Open .great-minds/decision-table.md and you will find columns: signal type, routing persona, escalation condition. When a project ships copy that reads like a press release, the table routes to Hemingway, not to Ogilvy. The decision is codified, not implicit.

Why this matters

A single omnibus prompt for all creative work produces mediocre results across the board — not terrible, but never tuned. The Constellation produces craft-native output because each plugin context is clean. The prose session never drifts into systems architecture. The orchestration session never writes a sentence.

If you get stuck

If it is not clear which plugin owns a given task, the problem is usually that the task spans two crafts. A product launch, for example, needs both great-marketers (positioning, channel strategy) and great-publishers (the actual artifacts: one-pager, press kit, landing page). Separate them. Run each plugin on its half.

If the persona file is producing generic output, the file itself is probably generic. Read it out loud. If it sounds like a Wikipedia article rather than the person's actual voice, rewrite it.

Deliverable

Name the five shipped plugins and their crafts without looking. Then name the decision that separates them — what makes great-authors its own plugin rather than a section of great-minds.

Further reading

This course is drawn from two essays on sethshoultes.com: "The Constellation" (the architectural argument) and "Great Minds Constellation: Ten Plugins, One Marketplace" (the plugin-by-plugin tour). The marketplace itself is at github.com/sethshoultes/great-minds-constellation.

• "Three Shapes of the Same Pattern" — the moment the same plugin shape repeats across great-minds, great-authors, and great-filmmakers, and what that pattern actually is.
• "Stars Aligned: The Writers Wrote the Engineers" — the five "not-yet-lit" plugins shipped during the writing of the original Constellation post; the data point on whether the pattern is actually reusable.