Task board ops

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

A portable Claude Code plugin system for orchestrating software development through parallel specialist agents, enforced engineering standards, and automated quality gates. One command to plan. Parallel agents to build. Automated gates to ship.

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.

What its author says it does

Copied from the file, not written here

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.

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