Use this skill when you need to upload a build, publish to a track, or manage rollout.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongpd-release-flowExecute the skills CLI command in your project's root directory to begin installation:
Fetches gpd-release-flow from rudrankriyam/app-store-connect-cli-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gpd-release-flow. Access via /gpd-release-flow in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
699
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
699
stars
Use this skill when you need to upload a build, publish to a track, or manage rollout.
GPD_SERVICE_ACCOUNT_KEY).--package explicitly.gpd publish upload app.aab --package com.example.app
gpd publish release --package com.example.app --track internal --status completed
gpd publish promote --package com.example.app --from-track beta --to-track production
Use when you need precise control or multiple changes in one commit.
# 1. Create edit
EDIT_ID=$(gpd publish edit create --package com.example.app | jq -r '.data.editId')
# 2. Upload build without auto-commit
gpd publish upload app.aab --package com.example.app --edit-id $EDIT_ID --no-auto-commit
# 3. Configure release
gpd publish release --package com.example.app --track internal --status draft --edit-id $EDIT_ID
# 4. Validate and commit
gpd publish edit validate $EDIT_ID --package com.example.app
gpd publish edit commit $EDIT_ID --package com.example.app
gpd publish release --package com.example.app --track production --status inProgress --version-code 123
gpd publish rollout --package com.example.app --track production --percentage 5
gpd publish rollout --package com.example.app --track production --percentage 50
gpd publish rollout --package com.example.app --track production --percentage 100
gpd publish halt --package com.example.app --track production --confirm
gpd publish rollback --package com.example.app --track production --confirm
gpd publish status --package com.example.app --track production
gpd publish tracks --package com.example.app
--status draft first for risky releases.--confirm only after reviewing gpd publish status output.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in gpd-release-flow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
gpd-release-flow reduced setup friction for our internal harness; good balance of opinion and flexibility.
gpd-release-flow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
gpd-release-flow has been reliable in day-to-day use. Documentation quality is above average for community skills.
gpd-release-flow fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for gpd-release-flow matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend gpd-release-flow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in gpd-release-flow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added gpd-release-flow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
gpd-release-flow reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 46