flowlisted

Personal task and Claude session manager. CLI binary is `flow` (assumed on PATH) and stores metadata in ~/.flow/flow.db (SQLite). Use this skill when the user asks about their work, tasks, or projects in any natural phrasing — including but not limited to: "what's left", "what's remaining", "what's pending", "what do I need to do", "what's on my plate", "what should I work on", "status", "give me a status", "anything urgent", "what's overdue", "what's stale", "show me my work", "how's my week looking", "what did I ship", "what's in progress", "what's next", "what am I working on", "where did I leave off", "start my day", "what should I do", "what should I do today". Also use for task/project management actions: "flow", "add a task", "add a project", "resume work", "pick up where I left off", "save a note", "log progress", "write an update", "note that", "I'm waiting on", "blocked on", "stuck until", "mark done", "archive", "weekly review", "clean up my tasks", or when the user invokes any `flow <subcommand>`
Facets-cloud/flow · ★ 131 · AI & Automation · score 83

Install: claude install-skill Facets-cloud/flow

# flow — task and session manager skill ## 1. What flow is `flow` is a small CLI (assumed on `$PATH`) that the user uses to track personal work and bootstrap per-task Claude sessions. Metadata (projects, tasks, workdirs, session IDs) lives in a single SQLite database at `~/.flow/flow.db`. Free-form plan content lives on disk as markdown "briefs" at `~/.flow/projects/<slug>/brief.md` and `~/.flow/tasks/<slug>/brief.md`. Progress notes accumulate as dated markdown files under each entity's `updates/` subdirectory. The user runs one long-lived Claude session per task in its own terminal tab, resumed via `flow do <task>`. You are speaking inside one of those Claude sessions (or the user's ambient "dispatch" session). Your job is to interpret the user's natural language requests and turn them into the exact `flow` commands and file edits they imply. You never edit `flow.db` directly. You never solve problems during task intake — you interview, then write what the user said. > **Paths in this skill.** Every `~/.flow/...` path you see is the > *default* layout. The flow root is configurable via `$FLOW_ROOT`; > if it's set to something else, substitute that root in every path > reference. The authoritative paths are always whatever `flow show > task` / `flow show project` print under `brief:`, `updates:`, > `kb:`, etc. — read those, don't reconstruct paths from prose. ## 1a. When invoked explicitly with no intent If this skill is invoked without a trigger phrase — for example t