missions
Missions
Break large engineering work into planned, validated missions executed by specialized agents — each with clean context, tight scope, and independent validation.
Why This Exists
Single-agent sessions work well for narrow tasks, but real engineering work is often too large and messy for one context window. As an agent accumulates context, its focus and reliability degrade. Two specific failure modes:
- Irrelevant context buildup. Wide scope means the agent carries information that has nothing to do with its current sub-task. Signal-to-noise drops.
- Self-evaluation bias. An agent that just built something is a poor judge of whether it built it correctly. Its own reasoning biases it toward thinking what it did was right.
More from pengelbrecht/skills
agent-screencast
>
6clone-website
|
3gws-slides
>
3claude-code-tutor
>
2lore
Connect to a Lore backend — query data, mutate with governance, propose schema changes, contribute knowledge. Use when an agent needs to interact with a Lore instance for reading/writing data, proposing DDL, or learning. Triggers on "connect to lore", "query lore", "lore schema", "propose table", or any task involving a Lore API.
1metricly-author
Conventions for writing dbt YAML descriptions and the org's business_context doc. Use when editing dbt/models/**.yml, dbt/context/business_context.md, or any file that feeds Metricly's semantic layer or org context.
1