Foundry
Foundry turns high-level requirements into a Blueprint — a structured technical plan that guides implementation. Engineers and engineering managers use Foundry to expand PRDs into detailed specifications, ensuring that every feature has clear technical direction before coding begins.
Translate PRDs into technical Blueprints
Organize requirements into Feature Nodes
Define implementation details section by section
Keep Blueprints synced with codebase and PRD updates
Learn how to use Foundry step by step in this short video:
A finalized PRD (with Feature Nodes extracted from Refinery/Foundry).
Select a Blueprint Template – Defines general sections (shared implementation details) and feature sections (per-feature details)
Generate Feature Nodes - If they weren’t created earlier in Refinery, you can also generate them directly in Foundry before drafting the Blueprint
Write the Blueprint – Populate sections manually or with AI assistance. The Blueprint Agent helps draft text, and a codebase-aware agent can pull implementation details from indexed code
Update Blueprints – If the PRD changes, Feature Nodes may become “stale.” Foundry highlights this with staleness indicators and allows you to refresh nodes
A complete, structured Blueprint that feeds directly into Planner.
Extract Feature Nodes from your PRD in Refinery/Foundry
Open Foundry and choose a Blueprint Template
Populate general sections (e.g., architecture overview)
Click on a Feature Node (e.g., “Authentication”) and ask the Blueprint Agent to draft the section
If your repo is indexed, use the codebase-aware agent to pull in existing patterns
Transition from Blueprint → move to Planner to create Work Orders
Blueprint Templates – Pre-defined structure for general and feature sections (custom templates coming soon)
Blueprint Navigator – Browse and edit sections; staleness indicators highlight updates needed
AI Assistance – Write sections with the Blueprint Agent or codebase-aware agent
Codebase Integration – Link technical details with your indexed repository
Stale Node Detection – Alerts when PRD changes require Blueprint updates
Agent struggling with long context? → Select only the relevant sections and restart the chat for better results.
A section fails to update from codebase? → Manually trigger “Update from Codebase” via the section dropdown.
Update Feature Nodes whenever PRDs change to avoid drift
Use Blueprint Templates to maintain consistency across projects
Let AI handle first drafts; refine manually for accuracy
If you run into bugs or see something off, report it using the In-Product Feedback button so the team can investigate and fix it
Blueprint: A technical plan combining architecture, requirements, and implementation details
Blueprint Template: Defines general and feature sections in the Blueprint (custom templates coming soon)
Feature Node: A discrete feature extracted from the PRD (may be nested)
Staleness: Indicator that a PRD or feature node has changed and the Blueprint should be updated
General Section: Covers implementation details relevant to all features
Feature Section: Created per feature, containing its implementation details
Ready to turn specs into tasks? Learn about Planner →
