Artifacts
PRDs, specs, architecture documents, and knowledge base items.
Artifacts are documents that form a project's knowledge base. Lisa creates and maintains them as part of project planning.
Artifact types
| Type | Description |
|---|---|
| PRD | Product Requirements Document — goals, user stories, requirements |
| Architecture | Technical architecture — system design, data models, API contracts |
| Spec | Technical specification — detailed implementation plan |
| Design | Design document — UI/UX decisions, wireframes, patterns |
| Notes | General notes — meeting notes, research, decisions |
Creating artifacts
Ask Lisa to create artifacts as part of planning:
- "Write a PRD for the notification system"
- "Create an architecture doc for the payment integration"
- "Document the decision to use WebSockets over SSE"
Or create them manually through the UI with the rich Markdown editor.
Linking
Artifacts are linked to projects and optionally to milestones and issues. This gives Lisa context when working on related tasks:
- Project artifacts inform all conversations within that project
- Milestone artifacts provide context for milestone-scoped work
- Issue artifacts give developers detailed reference material
Markdown editor
The built-in editor supports:
- Full Markdown syntax (headings, lists, links, code blocks, tables)
- Task lists with checkboxes
- Code blocks with syntax highlighting
- Table editing
- Image embedding