Skip to main content
Projects give you a dedicated space to group related work under a single name. A project collects tasks (for everyday work) or features with requirements (for software development), so you always see the full picture in one track show call. Every task you add to a project inherits its slug for filtering and display — the project becomes the lens through which you view that body of work.

​
Project basics

A project has three core attributes:
  • slug — a kebab-case identifier you use in every CLI command (kitchen-reno, my-app). If you don’t supply one with --slug, Wrixton derives it from the title automatically.
  • title — the human-readable name shown in lists and headings.
  • notes (optional) — free-form text displayed when you run track show <slug>.
# Create a project (slug auto-derived from title)
track add project "Kitchen renovation"

# Specify your own slug
track add project "Kitchen renovation" --slug kitchen-reno --notes "Spring 2026 remodel"

# Interactive wizard that prompts for slug, kind, notes, and initial tasks/features
track setup "Kitchen renovation"

​
Project kinds

Wrixton has two project kinds, set with --kind at creation time:

standard

The default. Holds a flat list of tasks ordered by priority. Use this for multi-step personal goals, home projects, and anything that isn’t a software codebase.

engineering

Organises work into features → requirements with an optional spec and design field on each feature. Tasks can attach to individual features. Use this for software projects.
# Standard project (default)
track add project "Kitchen renovation" --slug kitchen-reno

# Engineering project
track add project "Personal site redesign" --slug personal-site --kind engineering

​
The feature → requirement hierarchy

For engineering projects, work is structured as:
1

Create the project

track add project "Personal site redesign" --slug personal-site --kind engineering
2

Add features

Features represent discrete chunks of functionality. Each gets a f- prefixed ID. You can attach a --spec (specification notes) and a --design (design notes) to a feature.
track add feature "Dark mode toggle" --project personal-site
track add feature "RSS feed" --project personal-site --spec "Atom 1.0, 20 latest posts"
3

Add requirements to each feature

Requirements are the acceptance criteria inside a feature. They have r- prefixed IDs and are toggled done individually.
track add requirement "Persist preference to localStorage" \
  --project personal-site --feature f-3c9d

track add requirement "Respect prefers-color-scheme media query" \
  --project personal-site --feature f-3c9d
4

Attach tasks to features

Implementation tasks (kind task, k- prefix) can be scoped to a feature with --feature.
track add task "Wire up CSS custom properties" \
  --project personal-site --feature f-3c9d --estimate 1h
Toggle individual requirements done (or back to open) with track req: 
track req r-9c2a    # toggles done ↔ open, prints [✓] or [ ]

​
Adding tasks to a project

For standard projects, tasks attach directly to the project: 
track add task "Pick countertops" --project kitchen-reno --due 2w -p 2
track add task "Get appliance quotes" --project kitchen-reno --estimate 1h
--project is required for all tasks. The task’s ID uses the k- prefix.

​
Viewing projects

# List all projects (completed projects sort to the bottom)
track projects

# Show a project's full detail — tasks, features, requirements
track show kitchen-reno
track show personal-site
track projects prints a summary line per project. Standard projects show open/total task counts; engineering projects show done/total feature counts.

​
Completing and reopening projects

When all the work is wrapped up, mark the whole project done: 
track complete kitchen-reno    # status → done; sinks to the bottom of `track projects`
track reopen kitchen-reno      # status → active; floats back up
Completing a project doesn’t delete anything. All tasks, features, and requirements remain visible in track show <slug> — the project just moves to the bottom of the list so it stays out of the way during daily triage.
Task items belonging to a project are not shareable via track share. Lists that can be shared are todos, chores, shopping, and groceries. Project tasks are always private to the project owner.