Help us improve
Share bugs, ideas, or general feedback.
From coliseum-from-grain
Wraps each surfaced dimension into a self-contained 9-section assignment envelope (scope, context, success criteria, tools, return format, handoff) so recipient subagents can execute without follow-up questions.
npx claudepluginhub a-organvm/a-i--skills --plugin coliseum-from-grainHow this skill is triggered — by the user, by Claude, or both
Slash command
/coliseum-from-grain:assignment-composition <path to phase-1-dimensions.md><path to phase-1-dimensions.md>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are turning each named dimension into a self-contained autonomous-work-assignment envelope. After this phase, each envelope must be dispatch-ready — a recipient subagent reads only that envelope and executes, without needing to come back asking questions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes provided content for SEO quality, E-E-A-T signals, readability, keywords, and structure. Scores and recommends improvements based on best practices.
Share bugs, ideas, or general feedback.
You are turning each named dimension into a self-contained autonomous-work-assignment envelope. After this phase, each envelope must be dispatch-ready — a recipient subagent reads only that envelope and executes, without needing to come back asking questions.
Every assignment envelope MUST contain all of the following sections. Missing any section means the envelope is incomplete and the no-pingpong gate will reject it.
A short slug: assignment-NNN-<dimension-slug>. Stable across the rest of the protocol.
What the recipient is being asked to produce. One paragraph. Concrete, not abstract. If you cannot write this in one paragraph, the dimension is probably not yet pruned enough.
What the recipient is not being asked to produce. Lists adjacent work this assignment explicitly omits. This is where you preempt the "should I also do X?" question.
Everything the recipient must know to execute. This is the section that, if incomplete, causes ping-pong. Include:
If the recipient is a fresh subagent with no memory of this conversation (assume so — they have none), they must be able to start work after reading this section alone.
A checklist of what makes this assignment "done." Each item must be:
Explicit list of tools the recipient may use. Default to a minimal set. If you list "all tools," that is a flag that scope is too broad.
The agent type from the available roster (Explore, general-purpose, code-reviewer, etc.) you recommend dispatching this envelope to. Treat this as advisory, not load-bearing. There is no guaranteed expertise delta between subagent types beyond their tool sets and system prompts — all are general Claude underneath. Calling a subagent an "epistemologist" does not make it think like one; it makes it talk like one.
Justify the choice in one sentence on the basis of tool fit (does the subagent have the tools the work needs?) or system-prompt fit (does the subagent's prompt frame the work in a useful direction?), NOT on the basis of imagined domain expertise. If the most honest choice is general-purpose or claude, write that.
If a dimension would genuinely benefit from a domain expert that does not exist in the roster, name the gap explicitly in this section. Do not invent a subagent that does not exist; do not paper over the gap with a generic dispatch labeled as expert.
What the recipient writes back, and where. Be explicit about:
A final block stating:
phase-1-dimensions.md for full context (so the recipient can read peer dimensions if relevant).BLOCKED block in your return artifact rather than coming back to the originator. Continue with the rest of the assignment if any part remains executable."The BLOCKED exception is not ping-pong — it is a logged blocker, recorded in the artifact, surfaced at reconciliation. Ping-pong is the recipient bouncing back mid-dispatch asking for clarification before producing anything. The envelope must prevent that.
Read phase-1-dimensions.md. For each dimension, extract:
For each dimension, write a full envelope using the 9-section standard. Do not skip sections. Do not abbreviate. Length is fine — completeness is what matters.
After all envelopes are drafted, read them as a set. Verify:
grain-context.md.If you find a sequential dependency, decide: either it's a real sequence (downgrade one envelope to Phase-4 follow-up, not Phase-3 parallel dispatch), or the dimensions need re-pruning (back to Phase 1).
Write phase-2-assignments.md in the working directory. Required structure:
# Phase 2 — Assignment envelopes composed
## Grain (verbatim)
> <quoted grain>
## Envelope set
### assignment-001-<dim-slug>
**Scope (positive)**: …
**Scope (negative)**: …
**Context the recipient needs**: …
**Success criteria**:
- [ ] …
- [ ] …
**Allowed tools**: …
**Recommended subagent type**: …
**Return format**: …
**Handoff envelope**: …
### assignment-002-<dim-slug>
…
## Cross-check log
- Sequential dependencies found: <list, with resolution>
- Overlapping success criteria found: <list, with resolution>
- Scope-union coverage check: <pass/partial/fail, with note>
Before returning, verify for each envelope:
The next step in the protocol invokes the pingpong-detector agent against this artifact. The detector will fail any envelope that misses these. Better to self-check now than to be sent back.
The most common failure of this phase is assuming the recipient shares your context. They do not. A fresh subagent has none of the conversation history. Every assumption you carry from the conversation must be made explicit in the envelope, or the recipient will either ping-pong back or — worse — execute on their own assumptions and return work that misses the mark.
references/handoff-envelope-spec.md — full envelope spec with examplesreferences/assignment-anatomy.md — anatomy of the primitive being composed