Skip to content
cccskills
FreePublished on GitHub

idle

The idle work loop - enumerate open issues and triage rows, classify fixable vs blocked, pick by value-vs-budget, dispatch. Standing user directive; invoke whenever otherwise idle.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Idle Work Loop

Standing directive: there is no "waiting" state. Between lane completions, after a release, after a merge train drains — pick the next item and work it. New problems found along the way become issues at identification time, keeping the queue self-replenishing.

1. Enumerate

powershell.exe -Command 'gh issue list -R jamie8johnson/cqs --state open --limit 50 --json number,title,labels'
grep -c '| open |' docs/audit-triage.md   # plus the rows themselves if any

2. Classify

  • Blocked-external (upstream PRs, dependency releases, missing hardware, user-parked) — skip. Known standing members: cuvs upstream chain, ort RC, anything needing a Mac or native Windows.
  • Umbrella/design — only enter with explicit scoping; closing umbrellas orphans phases.
  • Fixable — everything else. Note effort (easy / medium / hard) and value.

3. Pick

Judgment call, biased by: user-stated priorities first; then highest-value-per-token. Mind the rate window — heavy lanes (schema work, parser work, large refactors) want ~25%+ of a 5-hour window remaining; near a reset, prefer trivial sweeps or solo-fixable items. If the issue list is dry, run /archeo to refill it, or check docs freshness (/docs-review if a week stale).

4. Dispatch

  • Implementation → lane-implementer agent (opus), one branch per coherent batch; worktree isolation.
  • Risky lanes (live scoring path, schema migrations, cross-surface signatures) → fable code-reviewer pass before landing.
  • Security-adjacent → opus for the analysis lane.
  • Land via /land; close linked issues on merge (verify, don't assume).

5. Loop

On lane completion: land it, file its residuals, return to step 1. Update tears when the board changes shape.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

archeo

Free

Comment-archaeology sweep - find work items hiding in TODO/FIXME/for-now comments and plan-doc ledgers, judge them, file issues, queue trivial fixes. Good idle-loop activity.

The English summary is being prepared. Showing the original description.

jamie8johnson/cqs17Updated Jul 14, 2026

audit

Free

Run a multi-category code audit on the cqs codebase. Spawns parallel agents per batch.

The English summary is being prepared. Showing the original description.

jamie8johnson/cqs17Updated Jul 14, 2026

Run before modifying a function — impact + test-map + explain in one pass, presented as a modification checklist.

The English summary is being prepared. Showing the original description.

jamie8johnson/cqs17Updated Jul 14, 2026

Trust-boundary security audit of cqs — fans out unbiddable-auditor agents across 6 categories (RT-INJ/RT-FS/RT-RES/RT-DATA/RT-RELAY/RT-EXFIL), attacker mindset, run-the-attack PoC + regression guard.

The English summary is being prepared. Showing the original description.

jamie8johnson/cqs17Updated Jul 14, 2026

Run after making changes, before committing — reviews the current git diff for impact and risk via cqs review.

The English summary is being prepared. Showing the original description.

jamie8johnson/cqs17Updated Jul 14, 2026

cqs

Free

Unified cqs CLI dispatcher — semantic code search, call graph navigation, impact analysis, quality tools, notes, and infrastructure. Use `/cqs <command> [args]` for any cqs operation.

The English summary is being prepared. Showing the original description.

jamie8johnson/cqs17Updated Jul 14, 2026

See all skills by jamie8johnson

Report a problem with this skill