Menu
Run the repo Rust TODO finder during sprint-end or integration review and turn every discovered TODO into a QA finding rather than deferred work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guide a consuming repository through `sc-lint-version` adoption using the authoritative consumer-integration workflow, existing CLI testability seams, existing simulators or transcripts, and only thin normalization hooks when unavoidable.
Orchestrate sc-lint sprint work where team-lead coordinates, clint is the sole developer, and quality-mgr enforces the QA gate.
Session initialization for the team-lead identity. Confirms identity and detects whether a full team restore is needed. Only run when ATM_IDENTITY=team-lead.
Orchestrate pre-dispatch QA finding triage as team-lead. Launch one qa-triage agent per finding, collect phase-scoped Turtle records, aggregate by promoted branch, and only then dispatch branch-scoped fix assignments to clint.
Team-lead drives plan hardening after the current plan state already exists in repo docs.
Orchestrate multi-sprint phase execution as team-lead. Manages sprint waves, scrum-master lifecycle, PR merges, clint reviews, and integration branch strategy. This skill is for team-lead only, not for scrum-masters.
| name | todo-triage |
| version | 1.0.0 |
| description | Run the repo Rust TODO finder during sprint-end or integration review and turn every discovered TODO into a QA finding rather than deferred work. |
| depends_on | {"quality-management-gh":"1.x"} |
Audience: quality-mgr and team-lead.
Use this during sprint-end QA or integration review when Rust TODO hygiene must be checked explicitly.
In sc-lint, TODO comments are not an approved way to defer work.
Every discovered TODO is a policy violation until it is resolved through one of these outcomes:
fix-nowremove-nowrewrite-now-as-explanatory-commentDo not treat a TODO comment as backlog, planning authority, or silent scope deferral.
If the underlying concern is truly out of sprint scope, raise it as a QA finding and let the normal triage/planning flow capture the follow-up. Do not leave the TODO comment behind as the tracking mechanism.
Run this:
From repo root:
python3 scripts/find_todos.py
The script scans repo Rust source files only.
Regression coverage for this helper lives in:
scripts/test_find_todos.pyCarry-forward routing for findings discovered in this pass is produced by:
scripts/triage_carry_forward.pyOutput format:
file:line:tag:text
Tag rules:
TODO(P6) -> P6TODO(fix) -> fixTODO -> untaggedProduce a concise report grouped by tag:
The triage pass fails if any TODO remains unresolved at the end.