Skill Claude CodeCodex
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…
Skill Claude Code
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…
Skill Claude Code
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.
Skill Claude Code
Implement a written plan (from write-plan or interview-plan). Use when the user says execute or implement the plan. Runs the review gate itself. Do not use while still interviewing or writing the plan.
Skill Claude CodeCodex
Set up or reuse an isolated git worktree for a ticket so the current checkout stays untouched. 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).
Skill Claude Code
Post-merge retrospective on the SDLC skill chain itself, from one ticket's artifacts. 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.
Skill Claude Code
Interview the user into an ambiguity-free spec and implementation plan. Use only when the user explicitly invokes "interview-plan" or asks to "interview me" / "stress-test the plan" about a plan or design. Runs write-plan itself — do not also invoke /write-plan.
Skill Claude Code
Strict branch-diff review against the ticket spec. Use after a dev session, before a PR, or when the user asks to review the branch. execute-plan runs it as its review gate — do not also invoke it unless code changed after Verdict: ship.
Skill Claude Code
Write an implementation plan from a spec before touching code. Use when the user invokes write-plan with an existing spec and no interview, or when interview-plan hands off an assembled spec. Do not use to implement.
Skill Claude Code
Implement a prepare-plan plan: run tasks as parallel subagent waves, verify every gate yourself, commit per task, then run review-build until ship. Use when the user says implement or execute the plan (sdlc-lite chain).
Skill Claude Code
Turn an idea or ticket into a decision spec and a task plan, grounded in the codebase. Use when the user invokes prepare-plan or asks to plan or spec a change (sdlc-lite chain). Do not use to implement.
Skill Claude Code
Post-merge retrospective on the sdlc-lite chain from one ticket's artifacts; proposes amendments and deletions to the skills. Use after merge and deploy, or when an escaped defect traces to a ticket. Not the next step after implement-plan.
Skill Claude Code
Strict review of the branch diff against the ticket spec. implement-plan runs it as the review gate; invoke directly after a dev session or before a PR (sdlc-lite chain).
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: