mirror of https://github.com/garrytan/gstack.git synced 2026-09-12 16:08:59 +02:00

Files

T

Garry TanandClaude Fable 5 b60fe8bd64 fix(gen): small config scrubs — openclaw blobs to real files, setup host drift, dead artifacts

- The three openclaw markdown blobs hardcoded inside gen-skill-docs.ts (which
  silently reverted any hand edit to their tracked outputs on regen) move to
  openclaw/templates/*.md source files; output shasums byte-identical.
- setup's --host allowlists gain cursor + slate — both fully registered hosts
  with generated output, but './setup --host cursor' exited 1 because two
  hand-rolled lists in setup had drifted from hosts/index.ts.
- scripts/proactive-suggestions.json deleted: 31KB regenerated on every run,
  read by nobody (the catalog-trim design's reader was never built); its
  emitter and three determinism tests (which guaranteed a file nothing reads
  didn't churn) retired with stays-retired pins.
- claude/SKILL.md.tmpl deleted: a complete 8.9KB skill that never generated
  output (directory name collides with the host id 'claude'), in no registry.
  Recoverable from git if ever wanted under a non-colliding name.
- openclaw's frozen extraFields.version '0.15.2.0' stamp dropped;
  includeSkills: [] no-ops omitted (the generator treats [] as absent);
  llms.txt 55 -> 54 skills.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-14 21:12:22 -07:00

1.0 KiB

Raw Blame History

gstack-plan: Full Review Gauntlet

Injected by the orchestrator when the user wants to plan a Claude Code project. Append to existing CLAUDE.md.

Planning Pipeline

Read CLAUDE.md and understand the project context.
Run /office-hours to produce a design doc (problem statement, premises, alternatives).
Run /autoplan to review the design (CEO + eng + design + DX reviews + codex adversarial).
Save the final reviewed plan to a file the orchestrator can reference later. Write it to: plans/-plan-.md in the current repo. Include the design doc, all review decisions, and the implementation sequence.
Report back to the orchestrator:
- Plan file path
- One-paragraph summary of what was designed and the key decisions
- List of accepted scope expansions (if any)
- Recommended next step (usually: spawn a new session with gstack-full to implement)

Do not implement anything. This is planning only. The orchestrator will persist the plan link to its own memory/knowledge store.

1.0 KiB Raw Blame History

gstack-plan: Full Review Gauntlet

Planning Pipeline

1.0 KiB

Raw Blame History