This skill should be used when the user asks to "rollout a feature", "complete feature release", "propagate SDK feature", "track feature support", "what's missing for feature X", or mentions checking CLI/GUI/docs/blog support for SDK features. Guides agents through the multi-repository feature release workflow from SDK to docs to marketing.
This skill guides the complete feature release workflow across the OpenHands ecosystem repositories.
When a feature is implemented in the SDK, it may need propagation through several repositories:
OpenHands/software-agent-sdk) — Core feature implementationOpenHands/OpenHands-CLI) — Terminal interface supportOpenHands/OpenHands frontend directory) — Web interface supportOpenHands/docs) — Documentation updates (sdk/ folder)OpenHands/growth-utils blog-post/) — Marketing and announcementsFirst, identify what feature(s) to analyze. The user may specify:
v1.9.0For release tags:
# Clone SDK if not present
git clone https://github.com/OpenHands/software-agent-sdk.git
# View release notes
cd software-agent-sdk
git log --oneline v1.8.0..v1.9.0 # Changes between versions
git show v1.9.0 --stat # What changed in this release
For specific features: Search the SDK codebase, examples, and changelog to understand the feature scope.
Clone all relevant repositories to analyze current support:
# Clone repositories (use GITHUB_TOKEN for authenticated access)
git clone https://github.com/OpenHands/software-agent-sdk.git
git clone https://github.com/OpenHands/OpenHands-CLI.git
git clone https://github.com/OpenHands/OpenHands.git # Frontend in frontend/
git clone https://github.com/OpenHands/docs.git
git clone https://github.com/OpenHands/growth-utils.git
For each feature, check support status:
| Repository | Check Location | What to Look For |
|---|---|---|
| CLI | openhands_cli/ | Feature flags, commands, TUI widgets |
| GUI | OpenHands/frontend/src/ | React components, API integrations |
| Docs | docs/sdk/ | Guide pages, API reference, examples |
| Blog | growth-utils/blog-post/posts/ | Announcement posts |
Not all features warrant full rollout. Evaluate each feature:
High Impact (full rollout recommended):
Medium Impact (docs + selective support):
Low Impact (docs only or skip):
Skip rollout for:
Generate a structured proposal for the user:
## Feature Rollout Proposal: [Feature Name]
### Feature Summary
[Brief description of the feature and its value]
### Current Support Status
| Component | Status | Notes |
|-----------|--------|-------|
| SDK | ✅ Implemented | [version/PR] |
| CLI | ❌ Missing | [what's needed] |
| GUI | ⚠️ Partial | [what's implemented vs needed] |
| Docs | ❌ Missing | [suggested pages] |
| Blog | ❌ Not started | [whether warranted] |
| Video | ❌ Not started | [whether warranted] |
### Recommended Actions
1. **CLI**: [specific implementation needed]
2. **GUI**: [specific implementation needed]
3. **Docs**: [pages to create/update]
4. **Blog**: [recommended or not, with reasoning]
5. **Video**: [recommended or not, with reasoning]
### Assessment
- **Overall Priority**: [High/Medium/Low]
- **Effort Estimate**: [days/hours per component]
- **Dependencies**: [what must be done first]
Wait for explicit user approval before proceeding. Ask:
Only after user confirmation:
Create GitHub Issues:
# Create issue on relevant repo
gh issue create --repo OpenHands/OpenHands-CLI \
--title "Support [feature] in CLI" \
--body "## Context\n[Feature description]\n\n## Implementation\n[Details]\n\n## Related\n- SDK: [link]\n- Docs: [link]"
Implementation order:
AGENTS.md for development guidelinesuv for dependency managementmake lint and make test before commitsopenhands_cli/tui/frontend/ directorynpm run lint:fix && npm run build in frontend/frontend/src/i18n/sdk/ folder.mdx files)mint broken-links to validateopenhands/DOC_STYLE_GUIDE.mdblog-post/posts/YYYYMMDD-title.mdblog-post/assets/YYYYMMDD-title/---
title: "Post Title"
excerpt: "Brief description"
coverImage: "/assets/blog/YYYYMMDD-title/cover.png"
date: "YYYY-MM-DDTHH:MM:SS.000Z"
authors:
- name: Author Name
picture: "/assets/blog/authors/author.png"
ogImage:
url: "/assets/blog/YYYYMMDD-title/cover.png"
---
Feature: Browser Session Recording (SDK v1.8.0)
openhands.tools.browsersdk/guides/browser-session-recording.mdxRecommendation: Medium priority. Docs done, CLI/GUI low urgency (advanced feature), blog post optional.
# Check SDK feature presence
grep -r "feature_name" software-agent-sdk/openhands/ --include="*.py"
# Check CLI support
grep -r "feature_name" OpenHands-CLI/openhands_cli/ --include="*.py"
# Check GUI support
grep -r "featureName" OpenHands/frontend/src/ --include="*.ts" --include="*.tsx"
# Check docs coverage
grep -r "feature" docs/sdk/ --include="*.mdx"
# Check blog mentions
grep -r "feature" growth-utils/blog-post/posts/ --include="*.md"