skills/loop/SKILL.md
Autonomous implementation loop over a focus topic. Reads active scopes, enumerates tasks as todos, then iterates the TDD pipeline (tester→implementer→reviewer) until all tasks are complete. Use when autonomously implementing all pending work for a scope or topic without manual step-by-step oversight.
npx skillsauth add srnnkls/tropos loopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pending tasks:
!find scopes -maxdepth 3 -name "tasks.yaml" -type f 2>/dev/null | xargs -I{} sh -c 'echo "=== {} ===" && grep -A1 "status: pending" {} 2>/dev/null'
Active todos:
!cat .claude/todos.json 2>/dev/null | jq -r '.[] | "[" + .status + "] " + .content' 2>/dev/null
Git status:
!git status --short 2>/dev/null
Current branch:
!git branch --show-current 2>/dev/null
Recent commits:
!git log --oneline -5 2>/dev/null
Base drift (behind-count vs trunk — loop re-checks every iteration):
!b=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@.*/@@'); b=${b:-main}; git fetch origin "$b" --quiet 2>/dev/null; behind=$(git rev-list --count "HEAD..origin/$b" 2>/dev/null); echo "base=$b behind=${behind:-?}"
Focus: $ARGUMENTS
INVARIANT: The orchestrator NEVER writes code or tests. All implementation MUST be delegated to fresh subagents via the implement skill.
$ARGUMENTS, create one TodoWrite entry per taskoperations/iterate.mdimplement — TDD pipeline delegated per taskscope — Full scope lifecycle with checkpoint managementcontinue — Resume interrupted loop from checkpointtools
External code-review harness (`peer` zsh tool): canonical model registry, idle-stall watchdog, and self-parallelising fan-out to codex/gemini. Use when dispatching external (non-Claude) reviewers from the review or implement pipelines — call `peer run`/`peer <harness>` instead of `codex exec`/`gcloud`+Vertex directly.
testing
Unified validation dispatcher. Auto-detects validation type from argument or presents selection menu. Routes to test, implement (verify), or hooks-test.
development
Test-driven development methodology (RED-GREEN-REFACTOR). Use when implementing features, fixing bugs, or changing behavior - write failing test first, then minimal code to pass.
development
Create new Claude Code skills following project patterns and best practices. Use when building new skills, extracting reusable capabilities, or converting commands to skills.