メニュー
Stakeholder report generator. Collects product metrics, GitHub milestones, and DB stats where available, then formats PDF-ready markdown. Trigger when: /investor-report, stakeholder report, raport inwestorski, metryki produktu.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | investor-report |
| description | Stakeholder report generator. Collects product metrics, GitHub milestones, and DB stats where available, then formats PDF-ready markdown. Trigger when: /investor-report, stakeholder report, raport inwestorski, metryki produktu. |
Prepare a concise, evidence-backed report for stakeholders.
Configure for your project. Replace
<PRODUCT_STATS_FILE>and<DB_STATS_QUERY>with the actual paths in your repo.
| Metric | Source |
|---|---|
| product / inventory metrics | <PRODUCT_STATS_FILE> (e.g. generated JSON, or build artifact) |
| roadmap / milestones | GitHub milestones API |
| velocity / highlights | merged PRs in period |
| users / usage | DB admin query or analytics export, if credentials are available |
| deploy status | hosting provider MCP or GitHub deployments |
Load whatever generated stats file your project produces (JSON, CSV, build artifact). Example:
node -e "const s=require('./<PRODUCT_STATS_FILE>'); console.log(JSON.stringify(s, null, 2));"
gh api repos/<OWNER>/<REPO>/milestones \
--jq '.[] | select(.state == "open") | {title,open_issues,closed_issues,due_on}'
gh pr list \
--repo <OWNER>/<REPO> \
--state merged \
--search "merged:>=YYYY-MM-DD base:main" \
--limit 100 \
--json number,title,mergedAt,labels,url
Never print service-role keys. If credentials are missing, state DB metrics unavailable.
Possible sources:
/api/stats, Edge Function)Minimum useful metrics:
# Raport dla stakeholderów
**Okres:** YYYY-MM-DD - YYYY-MM-DD
**Wygenerowano:** YYYY-MM-DD HH:mm Europe/Warsaw
## Executive summary
- ...
## Metryki produktu
| Metryka | Wartość | Źródło |
|---|---:|---|
| <Twoja metryka> | ... | <źródło> |
## Postęp milestone
| Milestone | Postęp | Termin | Ryzyko |
|---|---:|---|---|
## Highlights
- ...
## Ryzyka
- ...
## Następne kroki
1. ...
generatedAt is older than the report period.Shared multi-agent presence and claim protocol. Use before any coding agent starts work in this repo, when coordinating Claude/Codex/Gemini sessions, or when checking who is already working on the repository. Triggers: agent session start, check agent presence, agent coordination, who's working on repo.
Claude Code adapter for the shared agent-presence protocol (for Codex CLI use `.agent/skills/dispatch-watcher/SKILL.md`, for Gemini CLI use `.agent/skills/dispatch-watcher-gemini/SKILL.md`). Use on Claude session start to run pre-flight, claim Slack-dispatched issues (@claude #N), and emit lifecycle events. Triggers: Claude session start, /dispatch, /agent-presence, message addressed to @claude in the dispatch channel.
Gemini CLI adapter for the shared agent-presence protocol (for Claude Code use `.agent/skills/dispatch-watcher-claude/SKILL.md`, for Codex CLI use `.agent/skills/dispatch-watcher/SKILL.md`). Use on Gemini session start to run pre-flight, claim Slack-dispatched issues (@gemini #N), and emit lifecycle events. Triggers: Gemini session start, /dispatch, /agent-presence, message addressed to @gemini in the dispatch channel.
Optional agent dispatch watcher — Phase 1 walking skeleton, Codex-flavored. Use on agent session start when a Slack-style dispatch channel assigns GitHub issues to a model handle such as @codex. For Claude use `.agent/skills/dispatch-watcher-claude/SKILL.md`, for Gemini use `.agent/skills/dispatch-watcher-gemini/SKILL.md`, for the full multi-agent contract see `.agent/skills/agent-presence/SKILL.md`.
PR merge supervisor workflow. Use to merge a GitHub PR safely — resolve review threads correctly, check CI, run an optional repo supervisor, and do post-merge cleanup. Trigger when: /merge, merge PR, complete a PR, finalize a PR.
Use when generating operational reports, release notes, demo readiness checks, stakeholder updates, infrastructure cost/expiry checks, or bilingual changelogs. Triggers: /release-notes, /investor-report, /demo-check, /cost-check, changelog, release notes, stakeholder report, monthly metrics, demo readiness, before demo, infrastructure costs, cost monitoring, certificate expiry.