What It Does

The export system converts your project tasks into standalone Markdown files. Each exported file includes:

YAML frontmatter — structured metadata (status, phase, priority, tags, dates)
Description — the task's detailed description
Session links — connected chat sessions with names and dates
Deliverables — tracked outputs with type, creator, and word count
Metadata footer — internal IDs and AI suggestion source (if applicable)

You can export individual tasks or your entire project.

How to Use It

Exporting a Single Task

1
Click a task card to open its detail panel
2
Click the Export button (download icon) at the bottom of the panel
3
The file is saved as Markdown (e.g., TOR-001.md) and opens in your file browser

Exporting All Tasks

When you export all tasks to a folder, TorlyAI creates:

One .md file per task, named by display key (e.g., TOR-001.md, TOR-002.md)
A README.md index file with a summary table of all tasks

The index includes:

Total task count and status breakdown
A table with columns: Key, Title, Status, Phase, Priority, and Team Member
Links to each individual task file

Default Export Location

~/.torlyai/workspaces/{id}/project/exports/tasks/

Export Format

YAML Frontmatter

Each exported file starts with YAML frontmatter containing all task metadata:

---
aliases:
  - TOR-001
  - Define core product vision
type: task
cssclass: torlyai-task
date: 2026-01-15
key: TOR-001
title: Define core product vision
status: done
phase: discovery
priority: high
team_member: strategist
assignee: Dumbledore
tags:
  - task/done
  - phase/discovery
  - priority/high
  - team/strategist
  - vision
  - foundation
created: 2026-01-15T10:30:00.000Z
updated: 2026-01-20T14:45:00.000Z
---

Obsidian Compatibility

The frontmatter is designed to work with Obsidian out of the box: aliases let you link by key or title, type: task enables Dataview queries, cssclass: torlyai-task applies custom styles, and hierarchical tags (e.g., task/done, phase/discovery) support rich filtering.

Content Sections

After the frontmatter, the file contains:

1
Description — the task description (or "No description provided")
2
Session Links — listed with role (Primary/Reference), session name, and date
3
Deliverables — numbered list with type icon, title, word count, creator, and preview
4
Metadata — internal ID, display status, order, and AI suggestion source

Auto-Export Options

You can configure automatic exports that trigger on specific events:

On Complete

Triggers when a task's status changes to "Done"

On Status Change

Triggers when a task moves between any columns

Tips

Use exports for backup — even though data is stored locally, Markdown exports provide a human-readable backup
Import into Obsidian — drop your export folder into an Obsidian vault and use Dataview to query tasks
Share with advisors — export individual tasks and send them to mentors or advisors for review
Track in git — the Markdown + YAML format is ideal for version control, making it easy to see what changed between exports
Use the index — the generated README.md gives a quick overview of all tasks without opening individual files

Tasks

The tasks you are exporting

Deliverables

Deliverable details included in exports

Dashboard

Index file mirrors dashboard status summary

Task Export