Communication & Collaboration Agent Skills for Codex CLI

Analyze code changes and detect intent drift using the pr-to-spec CLI — converts a branch, staged edits, or recent commits into a…

When reviewing a Pull Request, generate explanatory Markdown that visualizes the change's structure using sequence diagrams, class…

Generate a static interactive D3 walkthrough of a pull request.

Use when a branch is ready for a pull request and the human wants to review the change before approving/merging — "walkthrough", "review…

Set up an isolated git worktree for a pull request and open it in a new editor window for review.

Over-engineering review. Examines recently written code for complexity that the project's actual scale and needs don't justify, and…

Deconstructs PRDs and product requirement documents into verifiable vertical-slice GitHub implementation issues for engineering teams.

Guides AI agents through structured product requirement document creation with outline reviews, budget tiers, and validated diagrams.

Use when reviewing a branch, commit, working tree, or PR-ready diff before opening or updating a pull request; when asked for pre-PR…

Verify completed issue work, draft its pull request, and create it after confirmation.

Principal Engineer Role - Responsible for architecture design, technical planning, and requirements modeling

Triage and process code reviews awaiting the current user's reaction: discover pending GitLab/GitHub review requests and open mention…

Procore prod checklist \u2014 construction management platform integration.\n\

Structured product brief and PRD creation assistant.

Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints…

Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured.

Produces async communication to stakeholders, primarily non-attendees and secondarily some attendees who want a reference.

Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions.

Answer product questions with short, plain-language explanations of what the product actually does, based only on reading the code — never…

Answer a product question via /product-question, then boil the answer down to an ELI18 TLDR — one plain-English takeaway an 18-year-old…