teamcraft-jcg:stakeholder-update
Generate an audience-appropriate stakeholder update by pulling live Jira sprint data, GitHub PR/pipeline status, and Confluence artifacts. Produces human-facing communication from AI-native project artifacts — status reports, client updates, executive summaries, engineering updates. Works in Claude Cowork and Claude Code.
What this skill does
## Goal Produce a stakeholder update that gives the audience exactly what they need — no more. Different audiences need fundamentally different information: a client cares about delivered value and risk to their timeline; an executive cares about status and decisions needed; an engineering team needs specifics about what shipped, what's blocked, and what changed. The source of truth is always the live project data — not memory, not estimates. ## Hard Constraints - Pull live data from Jira before composing any update. Never estimate or describe sprint status from memory. - The update is generated FROM the project artifacts, never instead of them. If the PRD or tech decisions are stale, flag it — do not paper over it in the update. ## Identify the Project and Sprint Use `mcp__sooperset-mcp-atlassian__jira_get_all_projects` to surface available projects and ask the user which one this update covers. Then use `mcp__sooperset-mcp-atlassian__jira_get_agile_boards` to find the project's board and `mcp__sooperset-mcp-atlassian__jira_get_sprints_from_board` to identify the active or most recently completed sprint. Confirm with the user. ## Pull Live Data From Jira, gather the current state of the sprint: - Use `mcp__sooperset-mcp-atlassian__jira_get_sprint_issues` for the sprint's complete issue list with status, assignee, and issue type - Supplement with `mcp__sooperset-mcp-atlassian__jira_search` using JQL for additional detail: priority, labels, created/updated dates - Identify issues that are at risk: blocked, overdue, or showing no recent activity - Sprint goal from the sprint data From GitHub (via Bash, if available): - PRs: `gh pr list --state all --json number,title,state,createdAt,mergedAt,headRefName` filtered to the sprint period - Pipeline status: `gh run list --limit 20` for recent workflow run outcomes - If Bash is unavailable, omit GitHub data and note the gap From Confluence: ask if the user can point at the PRD and any other relevant documents for context. Load them if available with `mcp__sooperset-mcp-atlassian__confluence_get_page`. ## Determine Audience and Compose Use `$ARGUMENTS` and context to determine the audience type. Ask if not clear. The audience shapes every word: **Client / external stakeholder** — delivered value in business terms, risks to scope or timeline with mitigations, decisions the client needs to make. No internal jargon. No ticket numbers. Green / Yellow / Red overall status with plain-language rationale. **Executive / leadership** — overall health (G/Y/R), progress toward sprint goal, risks that need a decision or escalation, asks. Under 300 words. No ticket-level detail. **Engineering team** — what shipped, what's blocked and why, what changed in scope or priority, what's up next. Ticket-level specifics welcome. Technical language appropriate. **Cross-functional partners** — what affects them: scope changes, new dependencies on their team, timeline shifts, decisions they need to weigh in on. See `references/example-stakeholder-update.md` for structure and tone calibration by audience type. ## Review and Store Show the complete update for review. Offer to adjust tone, length, or level of detail. Ask whether to store this in Confluence. If yes, ask which space. Use `mcp__sooperset-mcp-atlassian__confluence_search` to surface available spaces if needed. Once confirmed, use `mcp__sooperset-mcp-atlassian__confluence_get_page_children` to browse structure and recommend a parent page. Create with `mcp__sooperset-mcp-atlassian__confluence_create_page`. ## Done Share the update text and Confluence page URL if stored. The update is derived from the live project state — rerun this skill any time the audience or period changes.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.