01 Purpose & scope
Why this exists, and what "dual spec" actually means.
Naro and Kanso both manage task lists, and both can import a small portable JSON file describing one. Rather than build a separate importer prompt for each app, this one format works for either — an AI assistant (ChatGPT, Claude, Gemini, or anything else that can write a file) generates the same JSON regardless of which app the person actually uses.
The format is known by either name: DrezTek Task List or Naro Task List. Both refer to the exact same file shape. Nothing in the JSON itself changes based on which name someone uses when asking — the machine-readable kind field is always the literal string "dreztek-task-list", regardless of what a person calls it out loud.
02 Structure
The minimal shape every file needs.
{
"version": "1.2",
"kind": "dreztek-task-list",
"list": {
"title": "Morning tasks"
},
"tasks": [
{ "title": "First task", "priority": "high", "completed": false },
{ "title": "Second task", "priority": "medium", "completed": false, "position": "focus" }
]
}
Save as a .json file and import via Tasks → Import in Naro, or Tasks → list menu → Import in Kanso.
03 Field reference
Every field an importer recognizes, root through task.
Root
| Field | Required | Description |
|---|---|---|
| version | yes | "1.2" for new files; importers accept "1.0", "1.1", and "1.2" |
| kind | yes | Always "dreztek-task-list" |
| exportedAt | no | ISO-8601 timestamp |
| list | yes | List metadata (see below) |
| tasks | yes | Array of tasks, may be empty |
list
| Field | Required | Description |
|---|---|---|
| title | yes | Short display name for the list |
| categories | no | String array, e.g. ["Work", "Personal"] |
| sortMode | no | title, priority, dueDate, or order |
Each task
| Field | Required | Description |
|---|---|---|
| title | yes | Actionable task description |
| priority | yes | none, low, medium, high, critical, or focus |
| completed | yes | true or false |
| inProgress | no | Default false; mutually exclusive with completed |
| dueDate | no | ISO date, e.g. 2026-07-15 |
| notes | no | Extra context or caveats (note also accepted on import) |
| category | no | Should match a name in list.categories if categories are used |
| tradeCategory | no | Optional trade/classification label; apps without this ignore it |
| position | no | focus or quickWin — see Section 4 |
Naming rule: camelCase only (dueDate, inProgress, quickWin). Never status, pending, or due_date. Never add a $schema field to an output file.
04 Position & priority
Two different concepts, easy to conflate — worth being precise about.
Priority is how urgent a task is. Position is where it lives on Naro's task page — its Focus and Quick Wins collections, sitting above the regular list.
Position values
| Value | Meaning |
|---|---|
| focus | Naro's single most-important-right-now slot |
| quickWin | Naro's Quick Wins collection — small, fast tasks |
| (omitted) | No grouping — the task sits in its regular list only |
There is no followUp value. Follow-up in Naro is a snooze-adjacent reminder function now, not a list-placement state — it isn't something an agent generating a fresh, not-yet-started list would ever need to set. Kanso has no Position feature at all and simply ignores this field.
Priority mapping between apps
| DrezTek | Kanso | Naro |
|---|---|---|
| none | (unset) | none |
| low | low | low |
| medium | medium | medium |
| high | high | high |
| critical | high | critical |
| focus | focus | critical |
Use priority: focus for the single most urgent task. Use critical for blockers. Use position: focus separately, only when the user actually wants Focus-collection placement.
05 Ask an agent
Copy this into ChatGPT, Claude, Gemini, or any assistant, alongside whatever context you want turned into tasks.
Create a downloadable JSON file I can import into Naro or Kanso (Tasks → Import).
Deliver a .json file attachment — do not only paste JSON in the chat.
Filename: dreztek-{list-name}-{date}.json
Required structure (DrezTek/Naro Task List v1.2 — also called a Naro Task List, same format):
{
"version": "1.2",
"kind": "dreztek-task-list",
"list": { "title": "Short list name" },
"tasks": [
{ "title": "Actionable task", "priority": "medium", "completed": false }
]
}
Required task fields: title, priority, completed
Optional task fields: inProgress, dueDate, notes, category, tradeCategory, position
Rules:
- camelCase only: dueDate, completed, inProgress, tradeCategory, quickWin
- Do not use status, pending, or due_date
- Do not add a $schema field
- priority: none | low | medium | high | critical | focus
Use focus for the single most important task right now; critical for blockers.
- position: focus | quickWin — Naro's Focus/Quick-Win grouping. Omit unless the
user specifically asked for a task to be in Focus or Quick Wins.
- Use notes on individual tasks for caveats or extra context
- Use category or tradeCategory only when my attachment or context clearly supports them
- Default completed to false and inProgress to false unless context says otherwise
- Choose priority honestly — not everything is high
- Derive tasks from my attachment or context
Reference example: https://naroid.com/schemas/dreztek-task-list-v1.example.json
06 Legacy versions
Older files still import cleanly.
- v1.0 —
version: "1.0", task fieldnoteinstead ofnotes - v1.1 — identical to v1.2 minus
position - Kanso export —
kind: "kanso-task-list",list.name, camelCase task fields - Naro export (legacy) — no
kind,list.title, snake_case fields (is_done,due_date)
All of the above normalize to v1.2 on import.
07 Implementation & links
The hosted files behind this page.
| File | URL |
|---|---|
| JSON Schema (Naro) | naroid.com/schemas/dreztek-task-list-v1.schema.json |
| Example (Naro) | naroid.com/schemas/dreztek-task-list-v1.example.json |
| JSON Schema (Kanso) | kanso.dreztek.app/schemas/dreztek-task-list-v1.schema.json |
| Agent guide (machine-readable) | naroid.com/agent/task-list.json |
Naro import: Tasks header → Import. Naro export: open a list → … menu → Export List. Kanso import: Tasks → list menu → Import.