Claude-Code

Helps you run ingest → stage → process → publish across Slack, Confluence, bookmarks, and video—deduped knowledge atoms, provenance, one orchestration command.

Helps you move Jira state and Confluence pages from the terminal—JQL previews, acli transitions, version-fetched REST updates—when the web UI is too many clicks away.

Helps you answer lakehouse questions with Athena by matching intent to tables, fetching schemas on demand, then running SQL without memorizing the whole catalog.

Helps you slice operational Postgres via a read replica—staleness, soft deletes, join paths—with saved SQL, logged commands, and CSVs while the admin UI is still loading.

A fake citation in a product brief forced the switch: parallel pulls from PubMed, preprints, and trials, then tables with DOIs I can open before I repeat a number.

I learned the hard way that one-shot multi-phase Claude Code returns fast code and expensive cleanup; discuss → plan → execute → verify with atomic commits is what made autonomy survivable for me.

Helps you freeze a repeated workaround as SKILL.md: specific trigger, runnable procedure, verification, and the failure modes you already paid for.

I filed a vague `/codex-task` on a Friday and spent Monday unwinding five conflicting guesses; the real bottleneck is always the same—context, legible scope, and explicit format—so a new teammate could ship without guessing.

Helps you wire shell commands to Claude Code events—session start, after edit, before risky tools—so formatters, tests, and context loads run without anyone typing them.

Helps you wire Slack, Confluence, Jira, and mail into Claude through MCP—one config stanza per system—so the model calls live APIs instead of recycling pasted excerpts.