Task board ops

Skill rynhardt-potgieter/sprint_workflow/plugins/sprint-workflow/skills/task-board-ops

Use this skill when working with task boards, sprint planning, or task management. Covers discovering task tracking, claiming tasks, status updates, and sprint workflows. Activates when users mention tasks, sprints, backlogs, or task IDs.From its SKILL.md

Install

npx -y skills add rynhardt-potgieter/sprint_workflow --skill task-board-ops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 322 tokens by cl100k_base, as published. Nobody here has run it

Discovering Task Tracking

Projects may track tasks in different ways. Search in this order:

Markdown task boards: Look for project_management/TASKS/, TODO.md, TASKS.md, SPRINT.md, BACKLOG.md
GitHub Issues: gh issue list --state open
In-code markers: Grep for TODO, FIXME, HACK comments
CLAUDE.md: May reference task tracking conventions

Markdown Task Board Format

When task boards use markdown tables, they typically follow:

| TASK_ID | Title | Status | Priority | Assignee | Detail |

Status Flow

not-started --> ready --> in-progress --> ready-to-test --> completed
                  |                          |
                  +--> blocked (with notes) --+

Task Claiming

Find available tasks (status: not-started or ready)
Read any detail file or description to understand scope
Update status to in-progress and set assignee
Commit the status change if using file-based tracking

Task Completion

Verify acceptance criteria are met
Run quality checks (build, type-check, lint, tests)
Update status to completed
Commit the status change

Rules

Always understand the task before starting work
Keep task tracking formatting intact when editing
Only one assignee per task at a time
Blocked tasks must note the blocker

What ships with it: 2 files

2.8 KB alongside SKILL.md

references/

phase-board-format.md1.6 KB
task-status-flow.md1.2 KB

Gives 0 of the 12 instructions most operations skills give in 322 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

Collect monitoring data throughout the simulationin 14 of 483, across 6 files
Set the random seed for reproducibilityin 14 of 483, across 6 files
Validate simulations against analytical solutionsin 12 of 483, across 4 files
Clarify goals, constraints, and inputsin 11 of 483, across 2 files
Implement contract tests for integration pointsin 11 of 483, across 2 files
Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
Avoid Python blocking calls in processesin 10 of 483, across 3 files
Use resource context managers for automatic cleanupin 9 of 483, across 2 files
Maintain consistent time unitsin 9 of 483, across 2 files
Validate outcomes against success criteriain 8 of 483, across 1 file
Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

search for task tracking in markdown files
search open GitHub issues for tasks
grep in-code markers for tasks
read task details to understand scope
set task status to in-progress
set task assignee

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.