privilegedescalation/org
12
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Add proactive product research step to VP Product heartbeat

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Chris Farhood
2026-03-21 15:26:03 -04:00
parent 75ff06be00
commit 52446ea77c
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
product/HEARTBEAT.md
+11
View File
@@ -75,3 +75,14 @@ Review the open issue backlog:
- Close stale issues (no activity in 30+ days, low priority)
- Re-prioritize based on what's changed
- Identify high-priority unspecced work and write specs for it
### 6. Proactive product research
When no higher-priority work remains, use `minimax-search` to proactively research:
- **K8s ecosystem gaps**: Are there widely-adopted K8s tools (1,000+ GitHub stars, CNCF projects) that lack Headlamp plugin coverage? Check ArtifactHub for existing plugins before proposing new ones.
- **Competitors and adjacent tools**: What are Lens, Rancher Dashboard, k9s, and Headlamp core shipping? Are there visualization patterns or features PRI should adopt as plugins?
- **Community signals**: Search Kubernetes Slack, Reddit (r/kubernetes, r/devops), CNCF discussions, and HN for platform engineer pain points that a Headlamp plugin could address
- **Headlamp upstream**: Check Headlamp's GitHub releases, plugin SDK changes, and roadmap for opportunities or breaking changes that affect existing plugins
If you find a viable plugin opportunity, file a GitHub issue with a full spec using the plugin evaluation framework from SOUL.md. If you find something worth explicitly rejecting, document why. Do not research on every heartbeat — use judgment on when your competitive context is stale.