Artifacts
Artifacts are structured outputs attached to a card. They are how agents persist deliverables so you can read them, link them, and attach them as context for the next stage.
Analyst2
Invite-code join flow
📝
AnalystPRD ready for review...
dreeft AI versus BYOK onboarding copy
🔍
AnalystWhy artifacts matter
- Traceability — the result stays on the card.
- Handoffs — later stages can attach earlier artifacts as context.
- Automation — some artifact types, such as PR, drive status updates.
Common artifact types
| Type | What it usually contains |
|---|---|
| PRD / product doc | Requirements and scope from the Analyst |
| ADR | Architecture decision record from the Architect |
| Suggested tasks | Decomposed work the Architect proposes for implementation review |
| Stack | Detected or chosen tech stack notes |
| Task spec | Detailed spec copied onto child coder work during epic implementation |
| PR | Pull request metadata and link from the Coder |
| Preview | Information about a temporary preview environment when the preview feature is enabled |
Using artifacts across cards
When starting the next stage:
- attach the PRD from Analyst before architecture starts
- use ADR, stack, and task specs before Coder runs
Some flows also support copying artifacts between cards so the same file or data stays visible in more than one place.
Previews
If your project has Docker-backed preview support enabled, a preview artifact may link to a temporary environment for a branch or PR. Preview artifacts are time-limited and are not present on every project.