Files
gstack/openclaw/gstack-plan-CLAUDE.md
Rocky 834c6db075
Some checks failed
Workflow Lint / actionlint (push) Has been cancelled
Build CI Image / build (push) Has been cancelled
Skill Docs Freshness / check-freshness (push) Has been cancelled
Periodic Evals / build-image (push) Has been cancelled
Periodic Evals / evals (map[file:test/codex-e2e.test.ts name:e2e-codex]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/gemini-e2e.test.ts name:e2e-gemini]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/skill-e2e-design.test.ts name:e2e-design]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/skill-e2e-plan.test.ts name:e2e-plan]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/skill-e2e-qa-bugs.test.ts name:e2e-qa-bugs]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/skill-e2e-qa-workflow.test.ts name:e2e-qa-workflow]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/skill-e2e-review.test.ts name:e2e-review]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/skill-e2e-workflow.test.ts name:e2e-workflow]) (push) Has been cancelled
Periodic Evals / evals (map[file:test/skill-routing-e2e.test.ts name:e2e-routing]) (push) Has been cancelled
Initial import from garrytan/gstack@026751e (main snapshot via local relay)
Source: https://github.com/garrytan/gstack/commit/026751e
2026-05-19 21:18:17 +02:00

1.0 KiB

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

  1. Read CLAUDE.md and understand the project context.
  2. Run /office-hours to produce a design doc (problem statement, premises, alternatives).
  3. Run /autoplan to review the design (CEO + eng + design + DX reviews + codex adversarial).
  4. 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.
  5. 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.