10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
Jeffrey Emanuel's multi-agent implementation workflow using NTM, Agent Mail, Beads, and BV. The execution phase that follows planning and bead creation. Includes exact prompts used.
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install clawdnw/agent-swarm-workflowInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
Core Insight: Every agent is fungible and a generalist. They all use the same base model and read the same AGENTS.md. Simply telling one it's a "frontend agent" doesn't make it better at frontend.
The swarm is distributed, robust, and self-organizing through Agent Mail and Beads.
Before starting a swarm:
planning-workflow skill)beads-workflow skill)am or ~/projects/mcp_agent_mail/scripts/run_server_with_token.sh)┌─────────────────────────────────────────────────────────────┐
│ BEADS │
│ (Task graph with dependencies, priorities, status) │
└─────────────────────────────────────────────────────────────┘
│
┌─────────┴─────────┐
▼ ▼
┌─────────────────────────────┐ ┌─────────────────────────┐
│ BV │ │ AGENT MAIL │
│ (What to work on) │ │ (Coordination layer) │
└─────────────────────────────┘ └─────────────────────────┘
│ │
└──────────────┬─────────────┘
▼
┌─────────────────────────────────────────────────────────────┐
│ NTM + AGENTS │
│ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ │
│ │ CC │ │ CC │ │ Cod │ │ Gmi │ │ CC │ │ Cod │ │
│ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ │
└─────────────────────────────────────────────────────────────┘
# Spawn a swarm with multiple agents
ntm spawn myproject --cc=3 --cod=2 --g...
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# Agent Swarm Workflow — Parallel Implementation
> **Core Insight:** Every agent is fungible and a generalist. They all use the same base model and read the same AGENTS.md. Simply telling one it's a "frontend agent" doesn't make it better at frontend.
>
> The swarm is distributed, robust, and self-organizing through Agent Mail and Beads.
---
## Prerequisites
Before starting a swarm:
1. **Comprehensive plan** created (see `planning-workflow` skill)
2. **Polished beads** ready (see `beads-workflow` skill)
3. **AGENTS.md** configured with all tool blurbs
4. **Agent Mail server** running (`am` or `~/projects/mcp_agent_mail/scripts/run_server_with_token.sh`)
5. **NTM** available for session management
---
## The Swarm Architecture
```
┌─────────────────────────────────────────────────────────────┐
│ BEADS │
│ (Task graph with dependencies, priorities, status) │
└─────────────────────────────────────────────────────────────┘
│
┌─────────┴─────────┐
▼ ▼
┌─────────────────────────────┐ ┌─────────────────────────┐
│ BV │ │ AGENT MAIL │
│ (What to work on) │ │ (Coordination layer) │
└─────────────────────────────┘ └─────────────────────────┘
│ │
└──────────────┬─────────────┘
▼
┌─────────────────────────────────────────────────────────────┐
│ NTM + AGENTS │
│ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ │
│ │ CC │ │ CC │ │ Cod │ │ Gmi │ │ CC │ │ Cod │ │
│ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ │
└─────────────────────────────────────────────────────────────┘
```
---
## Starting the Swarm
### Using NTM (Named Tmux Manager)
```bash
# Spawn a swarm with multiple agents
ntm spawn myproject --cc=3 --cod=2 --g...generate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.