Communication & Collaboration Agent Skills for HTTP / API

Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind…

Manage and triage open issues on kimseungbin/claude-skills

Use when preparing code for review before submitting PRs — covers pre-flight validation, change summary generation, test evidence…

Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off…

Head of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex.

Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations.

Reviews an open pull request against coding standards, security, and test coverage, then posts a structured review comment and either…

Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and…

Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon.

Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning.

Use @pchuri/jira-cli to view, search, create, update, and delete Jira issues, comments, sprints, and projects from the terminal.

Command reference for jira-cli: managing Jira issues, epics, sprints, and boards from the terminal, including JQL queries.

Read Jira or equivalent work-tracking data as source material.

Analyze Jira issue requirements and create structured implementation plans, reading any attached mockups/screenshots/spec docs first.

Syncs plan progress to a linked JIRA ticket.

Write Jira-ready stories, tasks or bugs from corpus-grounded facts, with clear scope, acceptance criteria, impacts and links.

Create and update Jira tickets with action-verb summaries and ADF descriptions (user story for Stories/Tasks; flexible bug layout with…

Fetch and work with Jira issues. Use whenever a Jira ticket id like DHEI-1234 or SDDHEI-1234 appears, or when asked to look up, read, or…

Review code in Joyce's voice — terse, scope-disciplined, Socratic, layer-aware.

Review code across 5 axes (correctness, readability, architecture, security, performance) before merging.

Review every non-trivial decision with a fresh-context adversarial review.