/product-manager
Creates issues from customer feedback, monitors issues and PRs, and produces the daily product recap.
$ npx -y skills add getnao/sylph --skill product-manager --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/product-manager
Context preview
The summary Claude sees to decide when to auto-load this skill.
Creates issues from customer feedback, monitors issues and PRs, and produces the daily product recap.
SKILL.md
product-manager.SKILL.mdProduct Manager
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
1. Read `product/ROLE.md` for responsibilities 2. Read `product/PROMPT.md` for the current routine 3. Read recent logs in `product/logs/` (last 3 days) 4. 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
1. **Load context** per the list above 2. **Run the requested argument** 3. **Use `github/create-issue.md`** for new issues - follow its templates 4. **Log the run** - save to `product/logs/YYYY-MM-DD_<argument>.md` 5. **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):
1. If the CAO changes how issues are prioritized, framed, or categorized, update this skill file 2. If she flags feedback sources that were missed (e.g. a Slack channel, a Granola transcript), add them to the Context loading section 3. Update `product/_insights.md` with patterns: which feedback signals matter most, how she triages 4. If a daily summary format or issue batch structure works well, save it to `product/_examples/`
Read more
Product Manager
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
1. Read `product/ROLE.md` for responsibilities 2. Read `product/PROMPT.md` for the current routine 3. Read recent logs in `product/logs/` (last 3 days) 4. 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
1. **Load context** per the list above 2. **Run the requested argument** 3. **Use `github/create-issue.md`** for new issues - follow its templates 4. **Log the run** - save to `product/logs/YYYY-MM-DD_<argument>.md` 5. **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):
1. If the CAO changes how issues are prioritized, framed, or categorized, update this skill file 2. If she flags feedback sources that were missed (e.g. a Slack channel, a Granola transcript), add them to the Context loading section 3. Update `product/_insights.md` with patterns: which feedback signals matter most, how she triages 4. If a daily summary format or issue batch structure works well, save it to `product/_examples/`
The open-source company brain. Run your entire company with AI agents, skills, and a self-improving context.
Repo: getnao/sylph
Other skills on sylph.
- /blog-writer
```yaml name: blog-writer description: > Writes, designs, and publishes blog articles for the company website. Handles the full lifecycle from writing through cover image creation, local preview, PR creation, and post-publish archiving. triggers: - blog post - blog article -
Open skill - /brand-designer
Process for creating any branded visual asset (social graphics, one-pagers, banners, etc.).
Open skill - /brand-guidelines
The canonical reference for [your-company]'s brand identity. Load this before creating any branded content.
Open skill - /chief-of-staff
Runs the CEO's daily operating rhythm - inbox triage, project tracking, weekly planning, and briefing delivery.
Open skill - /cmo
Owns the content calendar, weekly planning, daily drafting, docs maintenance, and website review.
Open skill - /create-campaign
Build targeted outbound campaigns from ICP definition through personalized sequences.
Open skill