kb-skills/gsd-openclaw/.planning/ROADMAP.md

Roadmap: gsd-openclaw

Overview

Build a bridge layer connecting OpenClaw's multi-channel messaging system to GSD's Claude CLI-based project management workflow. The journey starts with core infrastructure (state persistence and tmux session management), then adds the integration layer (skill definition and response formatting), followed by orchestration (command routing and bridging), and finally completes with full GSD command support.

Phases

Phase Numbering:

• Integer phases (1, 2, 3): Planned milestone work
• Decimal phases (2.1, 2.2): Urgent insertions (marked with INSERTED)

Decimal phases appear between their surrounding integers in numeric order.

• Phase 1: Core Infrastructure - State persistence and tmux session lifecycle management
• Phase 2: Integration Layer - SKILL.md definition, response formatting, and prompt templates
• Phase 3: Orchestration - Command routing, user authentication, and bidirectional bridging
• Phase 4: GSD Integration - Full slash command bridging, approval flows, and progress reporting

Phase Details

Phase 1: Core Infrastructure

Goal: Users can create, list, destroy, and resume tmux sessions with persistent state for isolated project workspaces Depends on: Nothing (first phase) Requirements: SESS-01, SESS-02, SESS-03, SESS-04, SESS-05, SESS-06, SESS-07 Success Criteria (what must be TRUE):

1. User can create a new tmux session for a project and get a dedicated workspace directory
2. User can list all active sessions with their project associations
3. User can destroy a session when project is complete, freeing resources
4. User can resume an interrupted session with full context restoration from JSON checkpoint
5. Multiple users can run projects concurrently without interference (isolated sessions) Plans: 4 plans

Plans:

• 01-01-PLAN.md — State persistence layer with atomic writes and backup rotation
• 01-02-PLAN.md — Workspace directory management for project isolation
• 01-03-PLAN.md — tmux session lifecycle management using libtmux
• 01-04-PLAN.md — CLI entry point with session recovery and orphan cleanup

Phase 2: Integration Layer

Goal: OpenClaw can load and invoke the skill with channel-adaptive response formatting Depends on: Phase 1 Requirements: OCLW-01, OCLW-02, OCLW-04 Success Criteria (what must be TRUE):

1. SKILL.md has valid frontmatter (name, description, triggers) and OpenClaw loads the skill successfully
2. Skill triggers on /gsd:* patterns and project management keywords
3. Response formatting adapts to channel capabilities (markdown for rich channels, plain for constrained ones) Plans: 3 plans

Plans:

• 02-01-PLAN.md — SKILL.md creation with /gsd:* trigger pattern (OCLW-01, OCLW-02)
• 02-02-PLAN.md — FeishuResponseFormatter with Card JSON 2.0 support (OCLW-04)
• 02-03-PLAN.md — Prompt templates for context recovery, command mapping, error recovery (OCLW-02)

Phase 3: Orchestration

Goal: Users can send GSD slash commands through chat and receive captured output with proper error handling Depends on: Phase 2 Requirements: BRDG-01, BRDG-02, BRDG-03, BRDG-04, BRDG-05, OCLW-03, OCLW-05, OCLW-06 Success Criteria (what must be TRUE):

1. User can send any GSD slash command through chat (e.g., /gsd:new-project) and receive the output
2. User receives clear error messages when commands fail (not silent failures)
3. User can approve/reject GSD workflow gates through chat responses
4. User receives periodic progress updates during long-running operations
5. Skill integrates with OpenClaw's security model (dmPolicy, allowlists) and works across all channels Plans: 3 plans

Plans:

• 03-01-PLAN.md — Command executor with output capture and error detection (BRDG-02, BRDG-03)
• 03-02-PLAN.md — Approval handler and progress monitor (BRDG-04, BRDG-05)
• 03-03-PLAN.md — Orchestrator integration with command routing (BRDG-01, OCLW-03, OCLW-05, OCLW-06)

Phase 4: GSD Integration

Goal: All GSD slash commands are fully bridged with complete workflow support Depends on: Phase 3 Requirements: BRDG-06 Success Criteria (what must be TRUE):

1. All GSD slash commands work through the bridge (no command left behind)
2. Complete GSD workflow is accessible from any supported chat channel Plans: 3 plans

Plans:

• 04-01-PLAN.md — UserContextManager for per-user project context tracking (BRDG-06)
• 04-02-PLAN.md — Orchestrator special command handling for /gsd:new-project and /gsd:use (BRDG-06)
• 04-03-PLAN.md — Long command support and button callback for Create New Project (BRDG-06)

Progress

Execution Order: Phases execute in numeric order: 1 -> 2 -> 3 -> 4

Phase	Plans Complete	Status	Completed
1. Core Infrastructure	4/4	Complete	2026-03-11
2. Integration Layer	3/3	Complete	2026-03-11
3. Orchestration	3/3	Complete	2026-03-11
4. GSD Integration	2/3	In Progress	-

---

Roadmap created: 2026-03-10 Last updated: 2026-03-11 - Completed 04-02 special command handling