sg-tasks

Keep the task list coherent after work moves, instead of letting tracking fall behind reality.

A task-management skill for updating `TASKS.md`, reflecting progress, and capturing the next sensible steps.

Problem

What problem this solves

Task tracking stops being useful when the list no longer reflects what was completed, what remains, or what changed in scope.

Outcome

What changes when it works

You get a task file that stays closer to reality and is more useful for the next work cycle.

Why It Matters

What this changes for a solo founder

This skill matters because stale tracking quietly recreates the same confusion as stale docs: you stop trusting the operating surface.

When to use it

After meaningful implementation progress
When `TASKS.md` has drifted from reality
When you want a clearer next-step list for the next session

What you give it

The current task state and recent work context
Any relevant local `TASKS.md` surface

What you get back

A cleaner task list
Better visibility into completed and remaining work
A more useful handoff surface for future execution
Clearer Codex session names when you use the `sessions` mode
A status label that makes open, blocked, and completed conversations easier to scan
The current status visible directly in the Codex session name when you resume a previous session

Typical examples

/sg-tasks
/sg-tasks update after skills rollout
/sg-tasks what remains for launch
/sg-tasks sessions /path/to/project
/sg-tasks sessions rename done

Limits

It improves tracking discipline, not delivery speed by itself
If priorities are unclear, ordering still needs a separate judgment pass
The `sessions` mode only targets Codex sessions whose project working directory matches the selected project
The `sessions rename` mode targets only the current Codex conversation and does not update project task records
A directory without a task tracker can still be reviewed by exact working-directory path; the mode does not create project governance just for session cleanup
For duplicate subjects, only the most recently active conversation stays open; inactive non-current sessions older than 30 days are closed without changing linked task completion

Arguments

Some arguments change the workflow, not just the wording.

These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.

`sessions <project-or-cwd>`

The `309-sg-tasks` skill reviews Codex sessions for the selected project and renames their visible titles with the exact tracker statuses: `todo`, `doing`, `in_progress`, `blocked`, or `done`.

Consequence

When you resume a previous session in Codex, its name shows the current status directly. The mode changes the session title only, not the conversation content. This is a status and naming layer, not a one-to-one merge of conversations into tasks; several sessions may relate to the same task, including forks.

`sessions rename <status>`

The `309-sg-tasks` skill renames only the current Codex conversation with `<STATUS> - <semantic work title>` using `todo`, `doing`, `in_progress`, `blocked`, or `done`.

Consequence

The current session becomes recognizable at a glance without changing other sessions, forks, or `TASKS.md`. The command derives the work title from the visible conversation and requires the current project working directory to match exactly.

Read the launch cheatsheet

Related Skills

See the rest of the loop around this move.

Plan & Decide

sg-backlog

Capture ideas without letting them hijack the current execution thread.

A local-first backlog management skill for parking non-urgent work while keeping active delivery focused.

Open skill page

Plan & Decide

sg-priorities

Reorder the backlog by impact and effort before momentum turns into scattered activity.

A local-first prioritization skill for sorting active and pending work with a more explicit impact-versus-effort lens.

Open skill page

Operate & Ship

sg-end

Close a task cleanly so the work is summarized, tracked, and ready for the next thread.

A task-closing skill for wrapping up implementation, documenting completion, and recording closure in the chantier flow when applicable.

Open skill page

Go Deeper

This public page explains the move. The repository explains the execution contract.

Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.

Documentation Overview Open skills on GitHub Return to the skills hub