chancegraff

stop-slop

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

Data & Documents Listed

Create polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.

Code & Development Listed

pr-review-response

End-to-end workflow for responding to PR review feedback. Reads all review comments and requested changes on the current branch's pull request, plans and implements fixes via specialist agents, runs verification, and responds to every review thread on GitHub like a thoughtful engineer. Use this skill when the user wants to address PR feedback, respond to review comments, handle requested changes, or update their branch after a code review. Also applies when the user says things like "address the PR comments", "fix the review feedback", "respond to the reviewers", "handle the PR reviews", or "update the PR based on feedback".

work-the-branch

Workflow for advancing in-progress work on the current branch, at any stage, through to review-ready. Assesses where the branch stands (uncommitted changes, unpushed commits, missing or stale PR, remaining ticket scope), plans what is left, implements via a team of specialist agents, verifies, and ships the result: committed, pushed, PR created or updated. Use when the user invokes /work-the-branch.

jira-ticket-workflow

End-to-end Jira ticket workflow that manages a cross-functional team of agents to plan, implement, review, and ship work defined by a Jira ticket. Use this skill whenever the user provides a Jira ticket number (e.g., USP-2313, AID-21, CRM-450) and wants the work completed, or when they mention working on a Jira ticket, implementing a ticket, picking up a ticket, or completing a task from Jira. Also use this when the user says things like "do this ticket", "work on this issue", "implement this", or references a JIRA-style identifier followed by a request to build/fix/change something. Even if the user just pastes a ticket number with no other context, this skill applies.

Data & Documents Listed

epic-orchestrator

Orchestrate parallel execution of a Jira Epic's tickets by dispatching headless Claude Code workers in isolated git worktrees. Analyzes tickets for dependencies, plans execution waves, spawns one worker per ticket with a skill file loaded as its system prompt, coordinates with workers via append-only markdown files, and manages the full lifecycle through to PRs and review response. Invoke manually via /epic-orchestrator.

session-debrief

An end-of-session candor ritual. Answers two questions about the work just completed: what you're least confident about right now, and the biggest thing the user probably doesn't realize about the situation. Use this skill when the user invokes it directly (e.g. /session-debrief) to close out a working session. It is a forcing function for honesty: surface the doubts and blind spots that normal task-completion mode tends to paper over, before the user walks away believing the work is more finished or more certain than it is.

team-dev-workflow

General-purpose team development workflow for making and shipping code changes. Coordinates a team of specialist agents to plan, implement, review, verify, and ship code. Gathers context from Jira tickets, Figma designs, PR reviews, and the codebase. Scales from small bug fixes to large features. Use when the user invokes /team-dev-workflow.

Code & Development Listed

plan-convergence

Class-audit review procedure for plan convergence. Review rounds run until the surviving findings are nitpick-only, meaning wording taste, phrasing, or cosmetic rewrap, with no falsified claim, no contradiction, and no ownership or commitment change. Invoke when starting or continuing review rounds on any plan.