Work Tracking

Overview

Use this skill when a multi-step plan needs a durable way to be tracked across sessions, repositories, agents, PRs, and implementation work.

The default operating model is:

• Repo markdown = canonical strategy/spec.
• GitHub Issues = execution queue for implementation-ready tasks.
• Memory = compact convention/pointer only, never the backlog itself.
• Linear = optional product/company planning layer, only when the user explicitly wants that visibility.

This is intentionally cross-repo. It applies when work starts as a conversation and needs to become durable, discoverable, and executable.

When to Use

Use this skill when: