TICGIT DOCS WRITEUPS

Writeups

Commands: ti writeup new, ti writeup list, ti writeup show, ti writeup edit, ti writeup promote, ti writeup link, ti writeup unlink, ti writeup close

Writeups are versioned notes that live next to tickets. Use them for investigation notes, design sketches, release notes, longer implementation plans, or anything that should be preserved without becoming an actionable ticket immediately.

When to use a writeup

Use a ticket when the next action is clear and tracked through the lifecycle. Use a writeup when the work is exploratory, narrative, or expected to evolve over several edits before it becomes ticket-sized.

Use a ticket forUse a writeup for
Known bugs and tasksResearch notes and findings
Work that needs assignment or priorityDesign alternatives and tradeoffs
Items that should move through stateLong-form implementation notes
Small, reviewable units of workDrafts that may later become tickets

Create

Create a writeup with a title and optional body. If the title or body is omitted, TicGit opens your editor.

NEW WRITEUP
$ ti writeup new --title "Auth migration plan" --body "Move sessions to signed JWTs."
Created writeup b4d1a2 (Auth migration plan)
Full id: b4d1a2f0-2d3b-4c8b-9b0d-...
 
$ ti writeup new --title "Parser cleanup" --file notes.md --tags design,parser

List and read

By default, ti writeup list shows open writeups. Pass --all to include closed writeups.

LIST WRITEUPS
$ ti writeup list
b4d1a2 open 1 v1 Auth migration plan [design,auth]
9c17ee open 2 v3 Parser cleanup [parser]
 
$ ti writeup list --all
SHOW WRITEUP
$ ti writeup show b4d1a2
Shows the latest version.
 
$ ti writeup show b4d1a2 --all
Shows every saved version.

Edit versions

Editing a writeup appends a new version instead of replacing the old one. That makes writeups useful for evolving notes where previous context still matters.

APPEND VERSION
$ ti writeup edit b4d1a2
Opens $EDITOR with the latest version prefilled.
 
$ ti writeup edit b4d1a2 --body "Updated plan after review."
Appended version 2 to writeup b4d1a2.
 
$ ti writeup edit b4d1a2 --file revised-plan.md

Link to tickets

A writeup can be linked to one or more tickets. Use this when a design note, investigation, or implementation record explains why a ticket exists or how it was handled.

LINK WRITEUP TO TICKET
$ ti writeup link b4d1a2 a3f29c
Linked writeup b4d1a2 to ticket a3f29c.
 
$ ti writeup unlink b4d1a2 a3f29c

Linked writeups show up in the TUI details pane and keep the long-form context close to the ticket without overloading ticket comments.

Promote into a ticket

When a writeup turns into actionable work, promote it. TicGit creates a new ticket from the writeup title and latest body.

PROMOTE
$ ti writeup promote b4d1a2
Promoted writeup b4d1a2 to ticket e70ac1 (Auth migration plan)
Full ticket id: e70ac13a-...

Close or archive

Close a writeup when it is no longer active. archive is an alias for close.

CLOSE
$ ti writeup close b4d1a2
Closed writeup b4d1a2.
 
$ ti writeup archive b4d1a2

Workflow

A common workflow is to start with notes, revise them as the idea becomes concrete, then either link the writeup to existing work or promote it into a ticket.

WRITEUP TO TICKET
$ ti writeup new --title "Search ranking notes" --tags research
Capture early findings in $EDITOR.
 
$ ti writeup edit 9c17ee --file ranking-v2.md
$ ti writeup show 9c17ee --all
 
$ ti writeup promote 9c17ee
$ ti checkout e70ac1
$ ti spec --file implementation-plan.md
$ ti state assigned