comm
01Skill Claude CodeCodex
Rules for communication and writing: chat replies, PR bodies, comments, decision records, product docs, agent rules. Trigger: "/comm", "writing convention", "communication convention".
Skill Claude CodeCodex
Rules for communication and writing: chat replies, PR bodies, comments, decision records, product docs, agent rules. Trigger: "/comm", "writing convention", "communication convention".
Skill Claude CodeCodex
Interview a stakeholder in their own language and file their needs as GitHub issues for the product team. Runs on the stakeholder's machine with only the gh CLI — no repository clone, no build tools. Trigger: "/intake", "stakeholder interview", "requirements intake".
Skill Claude CodeCodex
Run repo work through subagents so the manager stays free for the user. Split work into small tasks, give each worker an isolated git worktree, and require the worker to commit, pass a fresh review, and deliver through the repo's delivery mode. Read project rules from the repo. Trigger: "orchestrate", "fan out…
Skill Claude CodeCodex
Turn a product request into settled requirements, product doc changes, and ready tickets. Ask the user for each missing choice, check current product and decision docs, and give the TL a clear build plan. Do not write application code or merge. Trigger: "/pm", "product manager", "grill requirements", "requirements…
Skill Claude CodeCodex
The fresh reviewer's procedure: read the repo's review rules, scan added lines, review the exact committed diff, and return PASS, BLOCK, or ERROR, recorded where the repo rules say. Loaded by the reviewer that a worker starts under /orchestrate. Trigger: "/review-gate", "review gate", or a review request from…
Skill Claude CodeCodex
Lead engineering work as the tech lead. Hold the engineering bar (smallest design, YAGNI, DRY, performance, OWASP security), split ready tickets into worker tasks, send them through /orchestrate, check each PR, and own engineering decision records. Do not write application code or merge. Trigger: "/tl", "tech lead"…
Skill Claude CodeCodex
Weekly technical-debt revisit. Gather the week's friction signals (hot spots, repeated review findings, flaky and slow tests, worker hiccups), scan for deepening and deletion candidates in the design vocabulary, present a private report, settle each candidate with the user, and turn the takes into sized tickets and…
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: