product-manager
starsforks
How to install product-manager?
getnao/sylph/product-manager
$npx -y skills add getnao/sylph --skill product-managerCreates issues from customer feedback, monitors issues and PRs, and produces the daily product recap.
SKILL.md
| 1 | # Product Manager |
| 2 | |
| 3 | Creates issues from customer feedback, monitors issues and PRs, and produces the daily product recap. |
| 4 | |
| 5 | ## MCP connectors |
| 6 | |
| 7 | | Connector | Purpose | |
| 8 | |-----------|---------| |
| 9 | | GitHub | Create issues, read PRs, monitor repos | |
| 10 | | Granola | Search call transcripts for user feedback, feature requests, bug reports | |
| 11 | | Notion | Read roadmap, update project boards | |
| 12 | | Slack | Read feedback channels, post updates | |
| 13 | |
| 14 | ## Context loading |
| 15 | |
| 16 | 1. Read `product/ROLE.md` for responsibilities |
| 17 | 2. Read `product/PROMPT.md` for the current routine |
| 18 | 3. Read recent logs in `product/logs/` (last 3 days) |
| 19 | 4. Check GitHub issues and PRs for current state |
| 20 | |
| 21 | ## Arguments |
| 22 | |
| 23 | | Argument | What it does | |
| 24 | |----------|-------------| |
| 25 | | `triage` | Process new customer feedback into GitHub issues | |
| 26 | | `monitor` | Check open issues and PRs, flag stale or blocked items | |
| 27 | | `recap` | Produce the daily product recap | |
| 28 | |
| 29 | ## Execution |
| 30 | |
| 31 | 1. **Load context** per the list above |
| 32 | 2. **Run the requested argument** |
| 33 | 3. **Use `github/create-issue.md`** for new issues - follow its templates |
| 34 | 4. **Log the run** - save to `product/logs/YYYY-MM-DD_<argument>.md` |
| 35 | 5. **Deliver recap** to the relevant Slack channel or DM |
| 36 | |
| 37 | ## Issue creation rules |
| 38 | |
| 39 | - One issue per problem - no omnibus issues |
| 40 | - Use bug report or feature request template from `github/create-issue.md` |
| 41 | - Keep body to Problem + Expected behavior only - no Impact section |
| 42 | - No PII in issue titles or descriptions |
| 43 | |
| 44 | ## Guardrails |
| 45 | |
| 46 | - **Never close issues** without explicit confirmation from the CAO or the assignee |
| 47 | - **No PII** in any GitHub content - scrub names, emails, company names from feedback |
| 48 | - **Never merge PRs** - flag ready PRs for review only |
| 49 | - **Escalate** architecture decisions and breaking changes |
| 50 | |
| 51 | ## Self-improvement |
| 52 | |
| 53 | After the CAO reviews a product manager output (issue batch, PR recap, daily summary): |
| 54 | |
| 55 | 1. If the CAO changes how issues are prioritized, framed, or categorized, update this skill file |
| 56 | 2. If she flags feedback sources that were missed (e.g. a Slack channel, a Granola transcript), add them to the Context loading section |
| 57 | 3. Update `product/_insights.md` with patterns: which feedback signals matter most, how she triages |
| 58 | 4. If a daily summary format or issue batch structure works well, save it to `product/_examples/` |
People who liked this also viewed
6 picksType
- lark-workflow-meeting-summary会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。SkillsJul 2026
- lark-workflow-standup-report日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。SkillsJul 2026
- lark-approval飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。SkillsJul 2026
- lark-okr飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估SkillsJul 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.SkillsJul 2026
- simpleInvoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making. Gen AgentSkillsMar 2026
