ayberkcansever

tech-radar

Builds a Thoughtworks-style learning radar of what a principal software + AI engineer should learn next — crawl registry feeds, triage, confirm adoption, place Learn/Try/Watch/Skip blips, save dated HTML. Use when the user asks what to learn, scan the radar, recent topics worth learning, what is moving in tech, or wants learning recommendations without naming a topic. Not for briefing a named topic — that is the learn skill.

brainstorm

Use when the user explicitly asks for brainstorming, pre-ticket discovery, fuzzy product shaping, visual option exploration, or turning an idea into an approved design before implementation planning.

execute-plan

Implement a written plan (from write-plan or interview-plan) when the user says execute or implement it. Loads the plan, executes ready tasks in waves in the ticket venue, runs the plan's review gate itself. Do not use while still interviewing or writing the plan.

graph-retro

Post-merge retrospective on the SDLC skill chain (interview-plan → write-plan → execute-plan → review). Reads one ticket's plan and spec, attributes failure signals to the skill that should have prevented them, and proposes one-line amendments. Use after merge and deploy, when the user says "retro this ticket", or when an escaped defect traces to an old ticket. Do not run as the next step after execute-plan or the review.

interview-plan

Interview the user one question at a time to produce an ambiguity-free implementation plan across three lenses — business requirements, backward compatibility, and technical. The model actively investigates the codebase first (Discovery Phase), confronts the user with what it found, and pushes back with alternatives — it does not transcribe the user's words. After the interview, it hands the assembled spec to the write-plan skill, which authors the on-disk plan, then runs an Audit Pass over that file so it is self-contained for a fresh model or engineer. Use only when the user explicitly invokes "interview-plan" or asks to "interview me" / "stress-test the plan" about a plan or design.

Code & Development Listed

thermo-nuclear-code-quality-review

Branch-diff review in five lenses — spec conformance, simplify (YAGNI / over-engineering), maintainability, merge safety, then mandatory feature-docs sync. Use /thermo-nuclear-code-quality-review after a dev session, before a PR. Repo-agnostic.

write-plan

Write a bite-sized TDD implementation plan from a spec before touching code. Saves under docs/plans/<TICKET-ID>/ (gitignored WIP); promote to docs/features/<TICKET-ID>/ when stable. Use when the user invokes write-plan, or when interview-plan hands off an assembled spec. Do not use to implement.

learn

Learn a tech topic to a correct 101 level in minimal time. Researches open sources (official docs/releases, engineering blogs, YouTube talks, HN/Reddit, news, papers) restricted to recent material, then produces a brief with a 101 mental model, what changed, tradeoffs, an adopt/trial/hold/avoid verdict, a time-budgeted learn-it-fast resource path, adjacent topics, and a proposed hands-on PoC lab (scaffolded on request; code ships complete, the user predicts, runs, observes and explains back, then gets quizzed for retention). Use when the user asks to research, learn, get up to speed on, "give me a brief/report on", or wants a hands-on PoC/lab/quiz for a technology, tool, framework, protocol, model, or engineering trend.

git-worktrees

Set up an isolated git worktree so the current checkout stays untouched and several tickets can run at once on one repo. Detects existing isolation and reuses a ticket's worktree, creates or attaches .worktrees/<branch>, verifies setup. Use when the user asks for a worktree; execute-plan calls it when the checkout is not already on the ticket branch (consent implied there).