znut

6 mods across 1 repository, 2 stars between them.

comm

01

znut/agent-skills

Skill Claude CodeCodex

Rules for prose the PO reads: chat replies, PR bodies, PR and ticket comments, ticket bodies, decision records, product docs, code comments, cross-session pings, partner messages. Every role and every worker loads it before writing. Trigger: "/comm", "writing convention", "communication convention".

2 5d ago A 63 tokens

intake

02

znut/agent-skills

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".

2 5d ago A 0 tokens

orchestrate

03

znut/agent-skills

Skill Claude CodeCodex

Run repo work through subagents. Split work into small tasks, give each worker an isolated git worktree, check the result, and require the worker to commit, pass review, and deliver through the repo's delivery mode. Read project rules from the repo. Pair this skill with /tl for engineering work or /pm for product…

2 5d ago A 103 tokens

pm

04

znut/agent-skills

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…

2 5d ago A 78 tokens

review-gate

05

znut/agent-skills

Skill Claude CodeCodex

Check a finished branch before PR creation. Read the repo's current review rules, scan added lines, review the exact committed diff, and return PASS, BLOCK, or ERROR. On PASS, write a marker bound to the reviewed commit. Trigger: "/review-gate", "review gate", "pre-PR review", or a review request from /orchestrate.

2 5d ago A 78 tokens

tl

06

znut/agent-skills

Skill Claude CodeCodex

Lead engineering work. Check ready tickets, split them into worker tasks, send them through /orchestrate, check each open PR, and track work after the user merges. Own engineering decision records, but do not write application code or merge. Trigger: "/tl", "tech lead", "team lead", "dispatch the ready queue", or…

2 5d ago A 76 tokens