Menü
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.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Team-lead drives plan hardening after the current plan state already exists in repo docs.
Repair ATM teammate coordination after same-session compaction or resume when atm-dev still exists on disk and the saved leadSessionId still matches the current SESSION_ID, but named-teammate ATM reachability is broken.
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.
Run or inspect the Phase Z smoke harness for atm-core. Use when implementing or operating `just smoke`, `just smoke fast`, or `just smoke thorough`, when rendering `reports/smoke/*`, when checking the frozen Phase Z row map, or when triaging smoke findings against retained logs and report artifacts.
Create, manage, scan, update, and clean up git worktrees for parallel development with protected branch safeguards. Use when working on multiple branches simultaneously, isolating experiments, updating protected branches (main/develop), or when user mentions "worktree", "parallel branches", "feature isolation", "branch cleanup", "worktree status", or "update main/develop".
Orchestrate atm-core sprint work where team-lead coordinates, arch-ctm is the sole developer, and quality-mgr enforces the QA gate.
| 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 atm-core, 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.
Output 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.