Product Manager
SkillAI & modelsCreates issues from customer feedback, monitors issues and PRs, and produces the daily product recap.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Product Manager skill
About this capability
The open-source company brain. Run your entire company with AI agents, skills, and a self-improving context.
What this skill tells your AI
The instructions your AI receives, as published by getnao/sylph in .claude/skills/product-manager/SKILL.md and read by ahel’s review.
Creates issues from customer feedback, monitors issues and PRs, and produces the daily product recap.
MCP connectors
| Connector | Purpose |
|---|---|
| GitHub | Create issues, read PRs, monitor repos |
| Granola | Search call transcripts for user feedback, feature requests, bug reports |
| Notion | Read roadmap, update project boards |
| Slack | Read feedback channels, post updates |
Context loading
- Read
product/ROLE.mdfor responsibilities - Read
product/PROMPT.mdfor the current routine - Read recent logs in
product/logs/(last 3 days) - Check GitHub issues and PRs for current state
Arguments
| Argument | What it does |
|---|---|
triage | Process new customer feedback into GitHub issues |
monitor | Check open issues and PRs, flag stale or blocked items |
recap | Produce the daily product recap |
Execution
- Load context per the list above
- Run the requested argument
- Use
github/create-issue.mdfor new issues - follow its templates - Log the run - save to
product/logs/YYYY-MM-DD_<argument>.md - Deliver recap to the relevant Slack channel or DM
Issue creation rules
- One issue per problem - no omnibus issues
- Use bug report or feature request template from
github/create-issue.md - Keep body to Problem + Expected behavior only - no Impact section
- No PII in issue titles or descriptions
Guardrails
- Never close issues without explicit confirmation from the CAO or the assignee
- No PII in any GitHub content - scrub names, emails, company names from feedback
- Never merge PRs - flag ready PRs for review only
- Escalate architecture decisions and breaking changes
Self-improvement
After the CAO reviews a product manager output (issue batch, PR recap, daily summary):
- If the CAO changes how issues are prioritized, framed, or categorized, update this skill file
- If she flags feedback sources that were missed (e.g. a Slack channel, a Granola transcript), add them to the Context loading section
- Update
product/_insights.mdwith patterns: which feedback signals matter most, how she triages - If a daily summary format or issue batch structure works well, save it to
product/_examples/
Signals
- GitHub stars
- 196
- Forks
- 58
- Last commit
- May 2026
Advanced
- Catalog kind
- skill
- Gateway key
product-manager-getnao- Source
- github.com/getnao/sylph