Verbatim Excerpt 1: team-builder SKILL.md (Team Analysis Phase)
## When you receive a team-building request
Read `references/architecture.md` first to understand the system design philosophy. Then follow the generation workflow below.
## Step 1: Analyze the team description
Before generating anything, think through:
- **Which roles are genuinely agentic** (observe → decide → act loops) vs. which are **pipelines** (input → transform → output)?
Label them honestly. Both are valid, but they need different architectures...
- **What are the dependency relationships?** Which agents consume another agent's output?
Draw this graph mentally — it determines context_sources in each agent.yaml.
- **What are the domain-specific ethical constraints?** Every domain has them.
Medical teams can't diagnose. Legal teams can't give advice as attorneys...
- **What's the feedback signal?** How will the human know if an agent's output is good?
This determines the eval dimensions.
Prompting technique: "Think before generating" section forces a structured pre-generation analysis pass (agentic vs. pipeline classification, dependency graph, ethical constraints, feedback signal). This prevents superficial team generation where every role becomes an "agent" regardless of whether it actually needs an agentic architecture.
Verbatim Excerpt 2: prompt/agent-team-builder.md (Constitutional Design Pattern)
**Constitution** — This is the most important document. It defines what NO agent (including the meta-agent) can violate. Structure it as:
1. Scope of authority (advisory only unless explicitly configured otherwise)
2. Domain-specific ethical boundaries (research these — every domain has regulatory and ethical constraints)
3. Evolution rules (incremental changes, documented rationale, rollback path)
4. Data handling constraints
5. Quality/voice/brand integrity
6. Inter-agent coherence requirements
The constitution must be written so that the meta-agent cannot weaken it, the auditor enforces it, and only the human operator can amend it.
Prompting technique: Three-party constitutional design (meta-agent proposes, auditor enforces, human amends). The constitution is explicitly designed to be uncircumventable — the meta-agent's prompt contains a reference to a document it cannot modify, creating an immutable constraint even when the meta-agent has write access to other agents' prompts.
Verbatim Excerpt 3: Auditor Six-Dimension Framework
**Auditor system prompt** — Six evaluation dimensions:
1. Constitutional compliance
2. Feedback fidelity (did the meta-agent actually address the feedback?)
3. Drift detection (is the agent moving away from its purpose?)
4. Regression risk (could this change break something that works?)
5. Cross-agent coherence (are agents still aligned?)
6. Change magnitude (within the 30% threshold?)
The auditor must be explicitly independent — the meta-agent has no authority over it.
Prompting technique: Structured multi-dimension evaluation rubric for the auditor. Each dimension is a specific, actionable check — not general quality assessment. The independence constraint ("meta-agent has no authority over it") is a prompt-level constraint that prevents adversarial self-modification.