What Blueprints will be
A Blueprint is a reusable, multi-step recipe — a sequence of model calls, connector invocations, and conditional branches packaged as a single thing you can trigger by name. Think: “run my Weekly Competitor Brief blueprint” and Foundry executes a 4-step pipeline — crawl, summarize, score, deliver — without you having to re-orchestrate it every time.Examples we’re prototyping
| Blueprint | What it does |
|---|---|
| Weekly Competitor Brief | Crawl target sites → extract pricing/feature deltas → write a 1-page brief → post to Slack. |
| Lead Enrichment | For each new lead → look up the company → score fit → append notes → update CRM. |
| Content Repurposer | Take a long-form article → produce 5 X posts + 1 LinkedIn post + a YouTube short script. |
How it’ll differ from Skills + Tasks
- A Skill is an expertise — a way to behave.
- A Task is a trigger — when to run.
- A Blueprint is a plan — multi-step orchestration with branches and parallel steps.
Want early access?
Tell Foundry — “add me to the Blueprints waitlist” — and we’ll loop you in as private beta opens.Today’s workaround
For multi-step automation right now, stack:- A Skill that codifies the steps as instructions.
- The relevant Connectors so the assistant has the tools.
- A Scheduled Task to run the prompt on a cadence.
Related
Skills
Today’s reusable behavior.
Scheduled tasks
Today’s automation trigger.