to-tasklist

Topics in the source

• To Tasklist
• When to use this instead of to-issues/to-prd
• Process

Sibling of to-issues, for projects that structurally can't have a tracker — same tracer-bullet discipline, different output: a durable file instead of a tool call. to-issues and to-prd both publish to a GitHub-style issue tracker and require one to exist. Some projects never will have one (e.g. finance-os: local-only git, holds real financial data, no public repo — see project memory). For those, don't fall back to the session-scoped TaskCreate/TaskList tools either — that state doesn't survive a session boundary or a machine switch, which defeats the point of finishing a design (being ready to execute whenever work resumes, not just this session). Check for a real tracker first (git repo + triage labels, per setup-matt-pocock-skills). If one exists, use to-issues instead. Only use this skill when there is none. 1. Draft vertical slices — same tracer-bullet rules as to-issues: each task is a thin, end-to-end, independently-completable slice, not a horizontal layer. Group into tracks when the work spans multiple systems (e.g. a track per repo/component touched). Self-check granularity before quizzing (same check to-issues runs). A drafted task is too coarse if any of these hold: mor

This is an excerpt. Refer to the complete source and its current requirements.