gstack-workflow-assistant▌
aradotso/trending-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Skill by ara.so — Daily 2026 Skills collection
gstack Workflow Assistant
Skill by ara.so — Daily 2026 Skills collection
Transform Claude Code from a generic assistant into a team of specialists you can summon on demand. Eight opinionated workflow skills that act as CEO, Engineering Manager, Release Manager, and QA Engineer with slash commands for planning, review, shipping, and testing.
What It Does
gstack provides specialized AI personas and workflows:
- CEO Review: Rethink problems and find the 10-star product hiding in requests
- Engineering Planning: Lock in architecture, data flow, and edge cases
- Code Review: Paranoid staff engineer-level review that catches production bugs
- Release Management: One-command shipping with tests and PR creation
- QA Testing: Automated browser testing with screenshots and systematic coverage
- Browser Automation: Give AI eyes to click through your app and catch breakage
- Session Management: Import real browser cookies for authenticated testing
- Team Retrospectives: Engineering manager-style retros with per-person insights
Installation
Requirements
- Claude Code
- Git
- Bun v1.0+
- macOS or Linux (x64/arm64) for browser automation
Global Installation
git clone https://github.com/garrytan/gstack.git ~/.claude/skills/gstack
cd ~/.claude/skills/gstack
./setup
Project Installation
cp -Rf ~/.claude/skills/gstack .claude/skills/gstack
rm -rf .claude/skills/gstack/.git
cd .claude/skills/gstack
./setup
Add to your CLAUDE.md:
## gstack
Use /browse skill from gstack for all web browsing. Never use mcp__claude-in-chrome__* tools.
Available skills:
- /plan-ceo-review - Product strategy review
- /plan-eng-review - Technical architecture planning
- /review - Thorough code review
- /ship - One-command branch shipping
- /browse - Browser automation and testing
- /qa - Systematic QA testing
- /setup-browser-cookies - Session management
- /retro - Engineering retrospectives
Core Commands
Planning Workflows
CEO Product Review
// Start with feature description, then review strategy
You: I want to add seller photo upload to the listing app
You: /plan-ceo-review
// AI responds as CEO: challenges assumptions, finds bigger opportunity
// "Photo upload" → "AI-powered listing creation from photos"
Engineering Architecture Review
You: /plan-eng-review
// AI responds as tech lead:
// - Architecture diagrams
// - State machines
// - Async job boundaries
// - Failure modes
// - Test matrices
Code Quality Workflows
Thorough Code Review
You: /review
// Paranoid staff engineer review:
// - Race conditions
// - Trust boundaries
// - Missing error handling
// - Production failure modes
One-Command Shipping
You: /ship
// Automated release process:
// 1. Sync main branch
// 2. Run test suite
// 3. Resolve review comments
// 4. Push branch
// 5. Open pull request
QA and Testing Workflows
Browser Automation
You: /browse https://myapp.com
// AI navigates your app:
// - Takes screenshots
// - Clicks through workflows
// - Identifies breakage
// - Tests responsive design
Systematic QA Testing
You: /qa
// Branch-aware testing:
// - Analyzes git diff
// - Identifies affected pages
// - Tests localhost:3000
// - Full exploration mode
// - Regression testing
You: /qa https://staging.myapp.com --quick
// Quick smoke test: 5 pages in 30 seconds
Session Management
You: /setup-browser-cookies staging.myapp.com
// Imports cookies from real browser (Chrome, Arc, Brave, Edge)
// Enables testing authenticated pages without manual login
Team Workflows
Engineering Retrospectives
You: /retro
// Engineering manager-style retro:
// - Analyzes git history
// - Per-person contributions
// - Growth opportunities
// - Team dynamics
// - Saves to .context/retros/
Configuration
Browser Settings
gstack creates isolated browser instances in .gstack/ directory:
// Automatic browser configuration
{
userDataDir: '.gstack/browser-data',
headless: false, // for debugging
viewport: { width: 1280, height: 720 },
timeout: 30000
}
Project Structure
your-project/
├── .claude/
│ └── skills/
│ └── gstack/
│ ├── skills/ # Workflow prompts
│ ├── browse/ # Browser automation
│ └── package.json
├── .gstack/ # Browser data (gitignored)
│ ├── browser-data/
│ └── screenshots/
└── .context/
└── retros/ # Retrospective history
Integration Patterns
Multi-Session Workflow
Use Conductor for parallel sessions:
// Session 1: Feature development
You: /plan-ceo-review
You: /plan-eng-review
// [implement feature]
// Session 2: Code review
You: /review
// [fix issues]
// Session 3: QA testing
You: /qa --full
// Session 4: Release
You: /ship
CI/CD Integration
# .github/workflows/gstack-qa.yml
name: gstack QA
on: [pull_request]
jobs:
qa:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- run: cd .claude/skills/gstack && ./setup
- run: echo "/qa --regression" | claude-code
Team Onboarding
# Add to team docs
## Development Workflow
1. `/plan-ceo-review` - Validate product direction
2. `/plan-eng-review` - Lock architecture
3. Implement feature
4. `/review` - Paranoid code review
5. `/qa` - Test branch thoroughly
6. `/ship` - One-command release
7. `/qa staging.app.com` - Staging verification
Advanced Usage
Custom QA Scenarios
// Feature-specific testing
You: /qa --focus=checkout-flow
You: /qa --mobile-only
You: /qa --accessibility
// Performance testing
You: /browse https://app.com
// Then: "Run lighthouse audit on this page"
Cross-Browser Testing
// Test in multiple browsers
You: /setup-browser-cookies app.com
You: /browse app.com --browser=chrome
// [switch session]
You: /browse app.com --browser=firefox
Regression Testing
// Before major changes
You: /qa --baseline
// [make changes]
You: /qa --compare-baseline
// AI identifies visual/functional regressions
Troubleshooting
Binary Issues
# Rebuild browser automation binary
cd .claude/skills/gstack
rm -rf browse/dist
./setup
Permission Errors
# Fix executable permissions
cd .claude/skills/gstack
chmod +x setup browse/dist/browse
Missing Dependencies
# Reinstall Node dependencies
cd .claude/skills/gstack
rm -rf node_modules
bun install
Browser Automation Failures
// Debug browser issues
You: /browse --debug
// Runs browser in non-headless mode for inspection
// Clear browser data
rm -rf .gstack/browser-data
Skill Registration Issues
How to use gstack-workflow-assistant on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add gstack-workflow-assistant
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches gstack-workflow-assistant from GitHub repository aradotso/trending-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate gstack-workflow-assistant. Access the skill through slash commands (e.g., /gstack-workflow-assistant) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★61 reviews- ★★★★★Hana Gonzalez· Dec 28, 2024
Solid pick for teams standardizing on skills: gstack-workflow-assistant is focused, and the summary matches what you get after install.
- ★★★★★Valentina Park· Dec 20, 2024
We added gstack-workflow-assistant from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Jin Menon· Dec 16, 2024
I recommend gstack-workflow-assistant for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Jin Abbas· Dec 12, 2024
gstack-workflow-assistant has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Hana Chawla· Dec 12, 2024
Keeps context tight: gstack-workflow-assistant is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Jin Rahman· Nov 19, 2024
Solid pick for teams standardizing on skills: gstack-workflow-assistant is focused, and the summary matches what you get after install.
- ★★★★★Liam Sanchez· Nov 11, 2024
gstack-workflow-assistant reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Jin Yang· Nov 7, 2024
Keeps context tight: gstack-workflow-assistant is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Hana Perez· Nov 7, 2024
gstack-workflow-assistant has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Henry Verma· Nov 3, 2024
I recommend gstack-workflow-assistant for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 61