mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-01 19:25:10 +02:00
Garry Tan
b3cd3fd68b
* feat: add 4 native OpenClaw skills for ClaHub publishing Hand-crafted methodology skills for the OpenClaw wintermute workspace: - gstack-openclaw-office-hours (375 lines) — 6 forcing questions, startup + builder modes - gstack-openclaw-ceo-review (193 lines) — 4 scope modes, 18 cognitive patterns - gstack-openclaw-investigate (136 lines) — Iron Law, 4-phase debugging - gstack-openclaw-retro (301 lines) — git analytics, per-person praise/growth Pure methodology, no gstack infrastructure. All frontmatter uses single-line inline JSON for OpenClaw parser compatibility. * feat: add AGENTS.md dispatch section with behavioral rules Ready-to-paste section for OpenClaw AGENTS.md with 3 iron-clad rules: 1. Always spawn sessions, never redirect user to Claude Code 2. Resolve repo path or ask, don't punt 3. Autoplan runs end-to-end, reports back in chat Includes full dispatch routing (Simple/Medium/Heavy/Full/Plan tiers). * chore: clear OpenClaw includeSkills — native skills replace generated Native ClaHub skills replace the gen-skill-docs pipeline output for these 4 skills. Updated test to validate empty includeSkills array. * docs: ClaHub install instructions + dispatch routing rules - README: add Native OpenClaw Skills section with clawhub install command - OPENCLAW.md: update dispatch routing with behavioral rules, update native skills section to reference ClaHub * chore: bump version and changelog (v0.15.10.0) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: add gstack-upgrade to OpenClaw dispatch routing Ensures "upgrade gstack" routes to a Claude Code session with /gstack-upgrade instead of Wintermute trying to handle it conversationally. * fix: stop tracking 58MB compiled binary bin/gstack-global-discover Already in .gitignore but was tracked due to historical mistake. Same issue as browse/dist/ and design/dist/. The .ts source is right next to it and ./setup builds from source for every platform. * test: detect compiled binaries and large files tracked by git Two new tests in skill-validation: - No Mach-O or ELF binaries tracked (catches accidental git add of compiled output) - No files over 2MB tracked (catches bloated binaries sneaking in) Both print the exact git rm --cached command to fix the issue. * fix: ClaHub → ClawHub (correct spelling) * docs: add ClawHub publishing instructions to CLAUDE.md Documents the clawhub publish command (not clawhub skill publish), auth flow, version bumping, and verification. --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
146 lines
6.5 KiB
Markdown
146 lines
6.5 KiB
Markdown
# gstack x OpenClaw Integration
|
|
|
|
gstack integrates with OpenClaw as a methodology source, not a ported codebase.
|
|
OpenClaw's ACP runtime spawns Claude Code sessions natively. gstack provides the
|
|
planning discipline and methodology that makes those sessions better.
|
|
|
|
This is a lightweight protocol encoded as prompt text. No daemon. No JSON-RPC.
|
|
No compatibility matrices. The prompt is the bridge.
|
|
|
|
## Architecture
|
|
|
|
```
|
|
OpenClaw gstack repo
|
|
───────────────────── ──────────────
|
|
Orchestrator: messaging, Source of truth for
|
|
calendar, memory, EA methodology + planning
|
|
│ │
|
|
├── Native skills (conversational) ├── Generates native skills
|
|
│ office-hours, ceo-review, │ via gen-skill-docs pipeline
|
|
│ investigate, retro │
|
|
│ ├── Generates gstack-lite
|
|
├── sessions_spawn(runtime: "acp") │ (planning discipline)
|
|
│ │ │
|
|
│ └── Claude Code ├── Generates gstack-full
|
|
│ └── gstack installed at │ (complete pipeline)
|
|
│ ~/.claude/skills/gstack │
|
|
│ └── docs/OPENCLAW.md (this file)
|
|
└── Dispatch routing (AGENTS.md)
|
|
```
|
|
|
|
## Dispatch Routing
|
|
|
|
OpenClaw decides at spawn time which tier of gstack support to use:
|
|
|
|
| Tier | When | Prompt prefix |
|
|
|------|------|---------------|
|
|
| **Simple** | One-file edits, typos, config changes | No gstack context injected |
|
|
| **Medium** | Multi-file features, refactors | gstack-lite CLAUDE.md appended |
|
|
| **Heavy** | Specific gstack skill needed | "Load gstack. Run /X" |
|
|
| **Full** | Complete features, objectives, projects | gstack-full pipeline appended |
|
|
| **Plan** | "Help me plan a Claude Code project" | gstack-plan pipeline appended |
|
|
|
|
### Decision heuristic
|
|
|
|
- Can it be done in <10 lines of code? -> **Simple**
|
|
- Does it touch multiple files but the approach is obvious? -> **Medium**
|
|
- Does the user name a specific skill (/cso, /review, /qa)? -> **Heavy**
|
|
- Is it a feature, project, or objective (not a task)? -> **Full**
|
|
- Does the user want to PLAN something for Claude Code without implementing yet? -> **Plan**
|
|
|
|
### Dispatch routing guide (for AGENTS.md)
|
|
|
|
The complete ready-to-paste section lives in `openclaw/agents-gstack-section.md`.
|
|
Copy it into your OpenClaw AGENTS.md.
|
|
|
|
Key behavioral rules (these go ABOVE the dispatch tiers):
|
|
|
|
1. **Always spawn, never redirect.** When the user asks to use ANY gstack skill,
|
|
ALWAYS spawn a Claude Code session. Never tell the user to open Claude Code.
|
|
2. **Resolve the repo.** If the user names a repo, set the working directory. If
|
|
unknown, ask which repo.
|
|
3. **Autoplan runs end-to-end.** Spawn, let it run the full pipeline, report back
|
|
in chat. User should never have to leave Telegram.
|
|
|
|
### CLAUDE.md collision handling
|
|
|
|
When spawning Claude Code in a repo that already has a CLAUDE.md, APPEND
|
|
gstack-lite/full as a new section. Do not replace the repo's existing instructions.
|
|
|
|
## What gstack generates for OpenClaw
|
|
|
|
All artifacts live in the `openclaw/` directory and are generated by
|
|
`bun run gen:skill-docs --host openclaw`:
|
|
|
|
### gstack-lite (Medium tier)
|
|
`openclaw/gstack-lite-CLAUDE.md` — ~15 lines of planning discipline:
|
|
1. Read every file before modifying
|
|
2. Write a 5-line plan: what, why, which files, test case, risk
|
|
3. Resolve ambiguity using decision principles
|
|
4. Self-review before reporting done
|
|
5. Completion report: what shipped, decisions made, anything uncertain
|
|
|
|
A/B tested: 2x time, meaningfully better output.
|
|
|
|
### gstack-full (Full tier)
|
|
`openclaw/gstack-full-CLAUDE.md` — chains existing gstack skills:
|
|
1. Read CLAUDE.md and understand the project
|
|
2. Run /autoplan (CEO + eng + design review)
|
|
3. Implement the approved plan
|
|
4. Run /ship to create a PR
|
|
5. Report back with PR URL and decisions
|
|
|
|
### gstack-plan (Plan tier)
|
|
`openclaw/gstack-plan-CLAUDE.md` — full review gauntlet, no implementation:
|
|
1. Run /office-hours to produce a design doc
|
|
2. Run /autoplan (CEO + eng + design + DX reviews + codex adversarial)
|
|
3. Save the reviewed plan to `plans/<project-slug>-plan-<date>.md`
|
|
4. Report back: plan path, summary, key decisions, recommended next step
|
|
|
|
The orchestrator persists the plan link to its own memory store (brain repo,
|
|
knowledge base, or whatever is configured in AGENTS.md). When the user is
|
|
ready to build, spawn a FULL session that references the saved plan.
|
|
|
|
### Native methodology skills
|
|
Published to ClawHub. Install with `clawhub install`:
|
|
- `gstack-openclaw-office-hours` — Product interrogation (6 forcing questions)
|
|
- `gstack-openclaw-ceo-review` — Strategic challenge (10-section review, 4 modes)
|
|
- `gstack-openclaw-investigate` — Operational debugging (4-phase methodology)
|
|
- `gstack-openclaw-retro` — Operational retrospective (weekly review)
|
|
|
|
Source lives in `openclaw/skills/` in the gstack repo. These are hand-crafted
|
|
adaptations of the gstack methodology for OpenClaw's conversational context.
|
|
No gstack infrastructure (no browse, no telemetry, no preamble).
|
|
|
|
## Spawned session detection
|
|
|
|
When Claude Code runs inside a session spawned by OpenClaw, the `OPENCLAW_SESSION`
|
|
environment variable should be set. gstack detects this and adjusts:
|
|
- Skips interactive prompts (auto-chooses recommended options)
|
|
- Skips upgrade checks and telemetry prompts
|
|
- Focuses on task completion and prose reporting
|
|
|
|
Set the env var in sessions_spawn: `env: { OPENCLAW_SESSION: "1" }`
|
|
|
|
## Installation
|
|
|
|
For OpenClaw users: tell your OpenClaw agent "install gstack for openclaw."
|
|
|
|
The agent should:
|
|
1. Install gstack-lite CLAUDE.md into its coding session templates
|
|
2. Install the 4 native methodology skills
|
|
3. Add dispatch routing to AGENTS.md
|
|
4. Verify with a test spawn
|
|
|
|
For gstack developers: `./setup --host openclaw` outputs this documentation.
|
|
The actual artifacts are generated by `bun run gen:skill-docs --host openclaw`.
|
|
|
|
## What we don't do
|
|
|
|
- No dispatch daemon (ACP handles session spawning)
|
|
- No Clawvisor relay (no security layer needed)
|
|
- No bidirectional learnings bridge (brain repo is the knowledge store)
|
|
- No JSON schemas or protocol versioning
|
|
- No SOUL.md from gstack (OpenClaw has its own)
|
|
- No full skill porting (coding skills stay native to Claude Code)
|