codingthefuturewithai/teamcraft-jcg:stakeholder-update
plugins/teamcraft-jcg/skills/stakeholder-update/SKILL.md
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.
tools
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add codingthefuturewithai/claude-code-primitives teamcraft-jcg:stakeholder-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 3:26 AM17.9s2 files scanned
SKILL.md
- name:
- teamcraft-jcg:stakeholder-update
- description:
- 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.
- argument-hint:
- [audience type and update period — e.g. 'client weekly update' or 'executive sprint summary']
- disable-model-invocation:
- true
- user-invocable:
- true
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_issuesfor the sprint's complete issue list with status, assignee, and issue type - Supplement with
mcp__sooperset-mcp-atlassian__jira_searchusing 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,headRefNamefiltered to the sprint period - Pipeline status:
gh run list --limit 20for 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 Skills
codingthefuturewithai/teamcraft:plan-iteration
development
VerifiedTrustedCommunity
Plan a time-boxed iteration (sprint, cycle, milestone) from the backlog and the PRD/roadmap behind it — gather the goal, the window, and the team's real capacity, then select, sequence, and size a committed set of work items to fit. Writes an `iteration` label onto each chosen work item. Use when the user says 'plan a sprint', 'plan the next iteration', 'plan our cycle', 'sprint planning', 'iteration planning', 'plan the next two weeks', 'set up a milestone', 'what should we take on this sprint', 'plan from the PRD', or otherwise wants to commit a scoped, time-boxed batch of work rather than create issues one at a time. This is the planning layer between requirements and the build loop — distinct from create-issue (one item) and pick-next-issue (pick one to build now).
SKILL.mdUpdated Jun 6, 2026
codingthefuturewithai/teamcraft:improve-teamcraft
tools
VerifiedTrustedCommunity
Capture feedback about Teamcraft itself and turn it into a well-structured GitHub issue on the plugin's repo. Vets whether the problem is really a Teamcraft skill defect (vs. misuse, the harness, or the user's own project) by root-causing against the actual skill source, then helps the developer decide whether to file and publishes via the GitHub CLI. Use when the user says 'improve teamcraft', 'a teamcraft skill did the wrong thing', 'file feedback on teamcraft', 'report a teamcraft bug', 'I have an idea to make teamcraft better', or when a Teamcraft skill clearly misbehaved and the user wants that captured upstream.
SKILL.mdUpdated May 31, 2026
codingthefuturewithai/teamcraft:learn-teamcraft
tools
VerifiedTrustedCommunity
Learn the Teamcraft plugin itself — how its workflow, skills, and artifacts fit together. A guided overview for a human getting started, or a system map for Claude orienting itself to how Teamcraft works before working in a Teamcraft repo. Teaching only; needs no project or environment access. Use when someone wants to understand Teamcraft (the tool, not their specific project), asks "how does Teamcraft work", "explain the workflow", "which skill do I use for X", or when Claude needs the big picture of how the skills hook together.
SKILL.mdUpdated May 29, 2026
codingthefuturewithai/plugins/teamcraft/skills/work-board
tools
VerifiedTrustedCommunity
--- name: teamcraft:work-board description: Launch (or re-launch) the user's live, multi-project work board. The dashboard is a single HTML file copied to a stable user-side location at ~/.claude/teamcraft-board.html and opened in the user's default browser. It has two views via a header toggle — a drag-and-drop Kanban Board and a live Status tab (analytics: work by status, throughput, cycle time, aging, blocked chains, recomputed on every poll). Each project is added via a header dropdown; the
SKILL.mdUpdated May 11, 2026