Quack Docs
Organize Work

Features & Roadmap

documentation/features/ as a browsable catalog and timeline, not just files on disk.

Quack encourages agents to keep a documentation/features/ folder — one markdown file per durable part of your product (042-search.md, 017-billing.md, and so on). The Features panel turns that folder into something you actually look at, not just something agents write to.

List and Timeline views

Browse every feature doc as a list, or as a Gantt-style timeline. Drag a bar to adjust a feature's start/end dates. Each entry shows its title, status (draft, active, done, archived), and one-line purpose at a glance.

Open and edit

Click a feature to open it in a drawer with a full Monaco editor — edit the Tasks checklist, Plan, or notes directly, no need to leave the app to touch the markdown file.

Mention a feature by its slug (@042-search) from the composer, or pin it as a chip, so the agent has the right context on what it's working on without you re-explaining the feature every time.

Why this instead of a kanban board

An older Plane-style board (work items, stories, cycles) existed and is being phased out in favor of this — feature docs are plain markdown, so they stay readable, diffable, and greppable, without a separate database to keep in sync.

On this page

say quack to us