\r \r

gstack-skills - Complete Development Workflow Suite\r

\r Complete development workflow suite adapted from Garry Tan's gstack for OpenClaw/WorkBuddy. Provides 15 specialized tools covering the entire development lifecycle from product ideation to deployment.\r \r

About gstack\r

\r gstack is Y Combinator CEO Garry Tan's open-source Claude Code configuration that helped him write 600,000+ lines of production code in 60 days (35% tests). This OpenClaw adaptation makes those powerful workflows available to any AI agent.\r \r

Quick Start\r

\r Use any of these commands directly:\r \r

• /gstack - Get help and see all available commands\r
• /office-hours - Validate product ideas and design thinking\r
• /plan-ceo-review - CEO perspective on feature planning\r
• /plan-eng-review - Engineering architecture review\r
• /review - Pre-merge code review\r
• /qa - Test application and fix bugs\r
• /ship - Automated release workflow\r
• /investigate - Systematic root cause analysis\r \r Example usage:\r \r

User: /office-hours I have an idea for an AI-powered code review tool\r
```\r
\r
```\r
User: /review my current branch\r
```\r
\r
```\r
User: /ship the user authentication feature\r
```\r
\r
## Command Routing\r
\r
When a user invokes any gstack command, this skill automatically routes to the appropriate specialized skill:\r
\r
| Command | Specialized Skill | Purpose |\r
|---------|-------------------|---------|\r
| `/gstack` | gstack-skills | Show help and command overview |\r
| `/office-hours` | office-hours | Product ideation and validation |\r
| `/plan-ceo-review` | plan-ceo-review | CEO perspective planning |\r
| `/plan-eng-review` | plan-eng-review | Engineering architecture review |\r
| `/plan-design-review` | plan-design-review | Design review |\r
| `/design-consultation` | design-consultation | Design system consultation |\r
| `/review` | review | Pre-merge code review |\r
| `/investigate` | investigate | Root cause analysis |\r
| `/design-review` | design-review | Design audit and fixes |\r
| `/qa` | qa | Test application and fix bugs |\r
| `/qa-only` | qa-only | Bug reporting only |\r
| `/ship` | ship | Automated release workflow |\r
| `/document-release` | document-release | Update documentation |\r
| `/retro` | retro | Team retrospective |\r
| `/codex` | codex | OpenAI Codex independent review |\r
| `/careful` | careful | Dangerous operation warnings |\r
| `/freeze` | freeze | Lock file editing scope |\r
| `/guard` | guard | Full safety mode (careful + freeze) |\r
\r
## When to Use This Skill\r
\r
This skill acts as a router and should be used when:\r
\r
1. **User invokes `/gstack`** - Show command overview and recommendations\r
2. **User needs guidance** - Help choose the right gstack command for their task\r
3. **User is new to gstack** - Provide context and explain the workflow philosophy\r
4. **User wants to learn** - Explain how gstack commands work together\r
\r
For specific command execution, this skill routes to the appropriate specialized skill.\r
\r
## Core Philosophy\r
\r
### Boil the Lake Principle\r
\r
> "Don't be half-invested, boil the whole lake" - Garry Tan\r
\r
AI-assisted development should pursue complete implementation, not shortcuts. When a problem is identified, actually fix it. Completing a task means truly completing it.\r
\r
### Intelligent Borrowing\r
\r
When borrowing features from other products, always consider:\r
1. Why does it work in the original product?\r
2. Will it succeed or fail in your product?\r
3. What adaptations are needed for success?\r
\r
## Recommended Workflow\r
\r
The complete development lifecycle:\r
\r
```\r
1. /office-hours       → Validate product ideas\r
2. /plan-ceo-review    → CEO perspective review\r
3. /plan-eng-review    → Engineering architecture review\r
4. /plan-design-review → Design review\r
5. /review             → Code review\r
6. /qa                 → Test and fix bugs\r
7. /ship               → Release to production\r
```\r
\r
## Command Overviews\r
\r
### Product Ideation Phase\r
\r
#### `/office-hours`\r
YC office hours tool for product idea validation. Use when:\r
- User says "brainstorm", "I have an idea", "help me think through this"\r
- Validating startup concepts\r
- Design thinking and problem reframing\r
\r
#### `/plan-ceo-review`\r
CEO/founder perspective planning. Use when:\r
- User says "think bigger", "expand scope", "strategic review"\r
- Evaluating feature ambition\r
- Challenging assumptions and finding 10x opportunities\r
\r
#### `/plan-eng-review`\r
Engineering manager perspective. Use when:\r
- User says "engineering review", "architecture review"\r
- Evaluating technical architecture\r
- Assessing implementation approaches\r
\r
#### `/plan-design-review`\r
Designer perspective. Use when:\r
- User says "design review"\r
- Checking UX and design quality\r
\r
### Development Phase\r
\r
#### `/review`\r
Pre-merge code review. Use when:\r
- User says "review this PR", "code review", "pre-landing review"\r
- Code is about to be merged\r
- Analyzing SQL security, race conditions, LLM trust boundaries\r
\r
#### `/investigate`\r
Debugging expert. Use when:\r
- User says "debug this", "investigate", "root cause"\r
- Systematic root cause analysis needed\r
- Complex troubleshooting\r
\r
#### `/design-consultation`\r
Design partner consultation. Use when:\r
- User says "design consultation"\r
- Building complete design systems\r
- Design thinking workshops\r
\r
### Testing & Release Phase\r
\r
#### `/qa`\r
QA engineer. Use when:\r
- User says "run QA", "test this", "check bugs"\r
- Code changes need verification\r
- Systematic testing and bug fixing\r
\r
#### `/qa-only`\r
QA reporter. Use when:\r
- User says "qa-only" or just wants bug reports\r
- No automatic fixing, just reporting\r
\r
#### `/ship`\r
Release engineer. Use when:\r
- User says "ship", "deploy", "push to main", "create PR"\r
- Fully automated release workflow\r
- Merge base branch, run tests, version management, create PR\r
\r
### Documentation & Review\r
\r
#### `/document-release`\r
Technical writer. Use when:\r
- User says "document release", "update docs"\r
- Updating project documentation\r
\r
#### `/retro`\r
Engineering manager. Use when:\r
- User says "retro", "retrospective"\r
- Team weekly reports\r
\r
### Power Tools\r
\r
#### `/codex`\r
OpenAI Codex independent review. Use when:\r
- Needing a second opinion\r
- Cross-validating review results\r
\r
#### `/careful`\r
Safety guardrails. Use when:\r
- About to perform dangerous operations\r
- Delete operations, file overwrites, dangerous commands\r
\r
#### `/freeze`\r
Lock file editing scope. Use when:\r
- Want to restrict which files can be edited\r
- Focus changes to specific directories\r
\r
#### `/guard`\r
Full safety mode. Use when:\r
- Maximum caution needed\r
- Combines careful + freeze for complete safety\r
\r
## Usage Examples\r
\r
### Example 1: New Feature Development\r
\r
```\r
User: I want to add user authentication to my app\r
\r
AI: Let's use the gstack workflow for this.\r
\r
Step 1: /office-hours\r
Let me help you validate and think through the authentication feature...\r
\r
[office-hours skill executes]\r
\r
Step 2: /plan-eng-review\r
Now let's review the technical architecture...\r
\r
[plan-eng-review skill executes]\r
\r
Step 3: Implementation\r
[Code implementation happens]\r
\r
Step 4: /review\r
Let me review your authentication code...\r
\r
[review skill executes]\r
\r
Step 5: /qa\r
Now let's test the authentication feature...\r
\r
[qa skill executes]\r
\r
Step 6: /ship\r
Ready to ship! Let me prepare the release...\r
\r
[ship skill executes]\r
```\r
\r
### Example 2: Quick Code Review\r
\r
```\r
User: /review my current branch\r
\r
AI: I'll review your current branch changes...\r
\r
[review skill executes automatically]\r
```\r
\r
### Example 3: Bug Investigation\r
\r
```\r
User: /investigate the login bug users are reporting\r
\r
AI: I'll systematically investigate the root cause...\r
\r
[investigate skill executes automatically]\r
```\r
\r
## Integration with Other Skills\r
\r
gstack-skills can work alongside other skills:\r
\r
- **data-analysis-workflows**: For analyzing product metrics during `/office-hours`\r
- **sql-queries**: When `/review` or `/investigate` needs database analysis\r
- **testing skills**: When `/qa` needs specialized testing knowledge\r
\r
## Skill Dependencies\r
\r
This skill depends on the following specialized skills, which must be available:\r
\r
- office-hours\r
- plan-ceo-review\r
- plan-eng-review\r
- plan-design-review\r
- review\r
- investigate\r
- qa\r
- qa-only\r
- ship\r
- document-release\r
- retro\r
- codex\r
- careful\r
- freeze\r
- guard\r
\r
## Error Handling\r
\r
If a specialized skill is not available:\r
\r
1. Inform the user which skill is missing\r
2. Suggest installing the missing skill\r
3. Offer to proceed with general capabilities as fallback\r
\r
## Best Practices\r
\r
1. **Start with `/office-hours`** for new features to validate ideas\r
2. **Use `/review` before merging** any code\r
3. **Always `/qa`** before shipping to production\r
4. **Use `/careful` or `/guard`** for risky operations\r
5. **Follow the complete workflow** for major features\r
\r
## Limitations\r
\r
- Some commands require specific tooling (git, test frameworks)\r
- `/ship` assumes git-based workflow\r
- Certain workflows are optimized for web applications\r
\r
## Learn More\r
\r
- Original gstack: https://github.com/garrytan/gstack\r
- Garry Tan's approach: "Boil the Lake" philosophy\r
- Y Combinator: https://www.ycombinator.com/\r
\r
---\r
\r
**Version**: 2.0.0 (OpenClaw/WorkBuddy adaptation)  \r
**Original Author**: Garry Tan, Y Combinator  \r
**Adaptation Team**: gstack-openclaw-skills Team\r