wgsd

---

name: wgsd description: We Get Shit Done - Social collaborative development workflow. Extends GSD with focus groups, concepts, and implementation tracking across Slack channels with Canvas integration. user-invocable: true

<objective> WGSD (We Get Shit Done) enables social software development through:

• Focus Groups: Long-lived topic channels (Security, Onboarding, Billing)
• Concepts: Feature ideas developed socially within focus groups
• Implementations: Short-lived execution of mature concepts (1-3 days)
• Canvas Integration: Live roadmaps that sync bidirectionally with git
• Shared Planning: All channels reference unified .planning/ structure
• Parallel Development: Multiple implementations without merge conflicts

Three-Tier Architecture:

1. Focus Groups (dozens) - Social ideation, roadmap building
2. Concepts (hundreds) - Focused feature discussions
3. Implementations (2-4 max) - Actual code execution

This is collaborative GSD - "We Get Shit Done" together. </objective>

<intake> What would you like to do?

Focus Group Commands:

• create-focus-group [name] - Create new focus group with channel, canvas, and planning structure
• list-focus-groups - Show all active focus groups and their status
• archive-focus-group [name] - Archive completed focus group

Concept Commands:

• create-concept [name] - Create concept within current focus group channel
• promote-concept [name] - Move concept to implementation queue
• list-concepts [focus-group] - Show concepts for focus group
• declare-impact [concept] - Declare cross-cutting focus group impacts
• update-impact [concept] - Modify existing impact declarations
• status [concept] - Show approval status and progress (Phase 14)

Approval Commands (Phase 14 - Slack-Native):

• approve [concept] - Approve concept for your focus group (or use ✅ reaction)
• approve [concept] --fg [fg] - Approve for specific focus group
• reject [concept] "reason" - Reject with required feedback
• request-review [concept] --fg [fg] - Request re-review after addressing feedback
• status [concept] - Show detailed approval matrix
• status - Show pending approvals in current channel

Implementation Commands:

• create-implementation [concept] - Start implementation from mature concept
• list-implementations - Show active implementations (max 2-4)
• complete-implementation [name] - Merge and clean up implementation

Canvas & Sync Commands:

• create-canvas [type] - Create canvas (master, implementation, focus-group, community, roadmap, all)
• sync-canvas [target] - Sync canvas from git state (all, fg, master, impl, community, roadmap)
• canvas-check - Check canvas integrity and detect drift
• canvas-restore [key] - Restore canvas from git state
• roadmap - Show cross-focus-group roadmap in main channel

Roadmap Branch Commands (Phase 13):

• merge-to-roadmap [concept] - Merge fully approved concept to roadmap branch
• roadmap-sync - Sync roadmap branch to develop (forward sync)
• roadmap-sync --dry-run - Preview sync changes without applying
• roadmap-sync --reverse - Sync develop changes back to roadmap

Migration Commands:

• migrate [repo-path] - Full GSD to WGSD migration wizard
• analyze [repo-path] - Analyze GSD project for migration readiness

Repository Commands:

• status - Show WGSD status across all focus groups and implementations
• setup-repo [repo-path] - Initialize WGSD structure in repository
• create-channel [name] [topic] - Create Slack channel via exec tool and API

Workflow Engine Commands:

• concept-development [concept] - Work on concept via planning PRs
• implementation-workflow [impl] [action] - Manage implementation lifecycle
• implementation-status [impl|all] - Show implementation progress
• approve [concept] - Vote to approve concept for implementation

Community Commands:

• collect [message-link] - Collect community feedback for triage
• triage - Show pending feedback triage queue
• move-to-focus-group [id] [fg] - Move feedback to focus group as concept
• invite-contributor [@user] [fg] - Invite community member to focus group
• request-access [focus-group] - Request access to a focus group
• approve-access [id] - Approve access request
• deny-access [id] [reason] - Deny access request
• community-status - Show community engagement statistics
• update-community-canvas - Refresh community roadmap canvas
• attribute [@user] [concept] [desc] - Add contributor attribution
• publish [type] [message] - Publish progress update to community

Usage Examples:

• /wgsd create-focus-group security - Create #mvn-security channel and structure
• /wgsd create-concept byof-filesystem - Create concept within focus group
• /wgsd promote-concept byof-filesystem - Move to implementation queue
• /wgsd roadmap - Show master roadmap in main development channel

Workflow:

1. Focus Group Creation - Long-lived topic channels for ideation
2. Social Concept Development - Ideas mature through team discussion
3. Implementation Promotion - Ready concepts become short-lived execution
4. Canvas Sync - Live roadmaps stay current with git planning
5. Cross-Channel Collaboration - Shared planning enables references </intake>

<routing> Based on user input, route to appropriate workflow:

| Intent | Workflow | |--------|----------| | "create focus group", "new focus group" | workflows/create-focus-group.md | | "create-focus-group", "focus-group" | workflows/create-focus-group.md | | "list focus groups", "show focus groups" | workflows/list-focus-groups.md | | "create concept", "new concept" | workflows/create-concept.md | | "create-concept", "concept" | workflows/create-concept.md | | "promote concept", "implement concept" | workflows/promote-concept.md | | "create implementation", "start implementation" | workflows/create-implementation.md | | "list implementations", "show implementations" | workflows/list-implementations.md | | "create canvas", "setup canvas", "create-canvas" | workflows/canvas-create.md | | "sync canvas", "sync-canvas", "update canvas" | workflows/canvas-sync.md | | "canvas check", "canvas integrity", "check canvas" | workflows/canvas-enforce.md | | "canvas restore", "restore canvas" | workflows/canvas-enforce.md | | "canvas workflow", "canvas help" | workflows/canvas-enforce.md | | "roadmap", "master roadmap", "live roadmap" | workflows/canvas-sync.md (roadmap mode) | | "setup repo", "initialize", "setup" | workflows/setup-repo.md | | "create channel", "new channel" | workflows/create-channel.md | | "setup core channels", "create dev channel" | workflows/setup-core-channels.md | | "archive channel", "archive" | workflows/archive-channel.md | | "restore channel", "unarchive channel" | workflows/restore-channel.md | | "migrate", "migration", "migrate from gsd" | workflows/migrate.md | | "analyze", "analyze project", "migration readiness" | workflows/migrate.md (analysis mode) | | "init", "initialize workspace" | workflows/init.md | | "workspace status", "wgsd status" | workflows/workspace-status.md | | "concept pr", "planning pr", "concept development" | workflows/concept-development.md | | "implementation pr", "code pr", "impl workflow" | workflows/implementation-workflow.md | | "implementation status", "impl status" | workflows/implementation-status.md | | "approve", "vote", "approval" | workflows/promote-concept.md | | "collect feedback", "record feedback" | workflows/moderate-feedback.md | | "triage", "triage queue" | workflows/moderate-feedback.md | | "move to focus group", "move-to-focus-group" | workflows/moderate-feedback.md | | "invite contributor", "invite-contributor" | workflows/invite-contributor.md | | "request access", "request-access" | workflows/access-request.md | | "approve access", "approve-access" | workflows/access-request.md | | "deny access", "deny-access" | workflows/access-request.md | | "community status", "community-status" | workflows/community-visibility.md | | "update community canvas", "community canvas" | workflows/community-visibility.md | | "attribute", "attribution" | workflows/community-visibility.md | | "publish update", "progress update" | workflows/community-visibility.md | | "declare impact", "declare-impact", "impact" | workflows/declare-impact.md | | "update impact", "update-impact", "modify impact" | workflows/update-impact.md | | "merge to roadmap", "merge-to-roadmap", "roadmap merge" | workflows/merge-to-roadmap.md | | "roadmap sync", "roadmap-sync", "sync roadmap" | workflows/roadmap-sync.md | | "approve", "lgtm", "+1", "ship it" | workflows/conversational-approve.md | | "reject", "block" | workflows/conversational-reject.md | | "status", "approval-status", "show-approvals", "matrix" | workflows/concept-status.md | | "request-review", "re-review" | workflows/conversational-reject.md |

</routing> <architecture> ## Repository Structure

WGSD creates shared planning structure:

{repo}/.planning/
├── PROJECT.md                      # Overall project context
├── focus-groups/                   # Long-lived topic areas
│   ├── security/
│   │   ├── ROADMAP.md             # Focus group roadmap (↔ Canvas)
│   │   ├── STATE.md               # Current status
│   │   ├── concepts/              # Feature concepts (v2.2 directories)
│   │   │   ├── byof-filesystem/   # v2.2 concept directory
│   │   │   │   ├── CONCEPT.md     # Primary concept description
│   │   │   │   ├── impact-matrix.md  # Cross-cutting impacts
│   │   │   │   ├── API-SPEC.md    # Optional API spec
│   │   │   │   └── acceptance-criteria.md  # Optional AC
│   │   │   ├── auth-v2/
│   │   │   │   ├── CONCEPT.md
│   │   │   │   └── impact-matrix.md
│   │   │   └── sso-integration.md # Legacy single-file (backward compat)
│   │   └── CHANNELS.md            # Slack channel mappings
│   ├── onboarding/
│   │   ├── ROADMAP.md
│   │   ├── STATE.md
│   │   ├── concepts/
│   │   │   ├── recommended-prompts.md
│   │   │   └── agent-setup.md
│   │   └── CHANNELS.md
│   └── billing/
│       ├── ROADMAP.md
│       ├── STATE.md
│       ├── concepts/
│       └── CHANNELS.md
├── active-implementations/         # Current execution (2-4 max)
│   ├── auth-v2-impl/
│   │   ├── REQUIREMENTS.md        # Traditional GSD structure
│   │   ├── ROADMAP.md
│   │   ├── STATE.md
│   │   └── concept-source.md      # Links to originating concept
│   └── billing-api-impl/
│       ├── REQUIREMENTS.md
│       ├── ROADMAP.md
│       ├── STATE.md
│       └── concept-source.md
├── MASTER-ROADMAP.md              # Cross-focus-group aggregation
└── WGSD-CONFIG.md                 # Channel mappings and settings

Git Integration

Branch Hierarchy (v2.2 + Phase 13 Three-Tier Branching):

main/develop (primary)
├── roadmap                        # ✨ Phase 13: Approved concepts backlog (PERMANENT)
├── concepts/                      # v2.2 concept branches (medium-lived)
│   ├── byof-filesystem            # Independent concept development
│   ├── auth-v2                    # Each concept gets its own branch
│   └── oauth-integration          # PRs merge to focus-groups/*
├── focus-groups/                  # Focus group branches (long-lived)
│   ├── security                   # Planning and roadmap
│   ├── onboarding                 # Concepts merge here after approval
│   └── billing                    # Never merges to develop directly
└── implementations/               # Implementation branches (short-lived)
    ├── auth-v2-impl               # ✨ Phase 13: Branches FROM roadmap
    └── billing-api-impl           # Merges back to develop (1-3 days)

Three-Tier Concept Flow (Phase 13):

concepts/{name}          ← Concept development
    │
    ▼ (PR on team approval)
focus-groups/{fg}        ← Focus group review
    │
    ▼ (full matrix approval)
roadmap                  ← Approved backlog (auto-merge on completion)
    │
    ▼ (create-implementation)
implementations/{name}   ← Code execution (branches FROM roadmap)
    │
    ▼ (merge)
develop/main            ← Production code

Roadmap Branch (Phase 13):

• Purpose: Holds all fully approved concepts ready for implementation
• Created: Automatically on wgsd init
• Merge In: Concepts auto-merge when matrix approval completes
• Branch From: Implementation branches start from roadmap
• Sync: Periodically synced to develop via wgsd roadmap-sync

Slack-Native Approval (Phase 14):

• Rich Prompts: Approval requests appear with context, progress bars, and quick actions
• Conversational Approve: /wgsd approve, ✅ reaction, or "LGTM" in thread
• Discussion Threads: Auto-created for each approval request
• Status Summaries: /wgsd status shows approval matrix with visual progress
• Rejection Workflow: Required feedback, author notification, re-review path
• Full Approval: Auto-triggers roadmap merge when all FGs approve

Worktrees:

{repo}/
├── .git/                          # Main git directory
├── worktrees/                     # v2.2 concept worktrees
│   ├── byof-filesystem/           # → concepts/byof-filesystem branch
│   ├── auth-v2/                   # → concepts/auth-v2 branch
│   └── oauth-integration/         # → concepts/oauth-integration branch
├── concepts/                      # Focus group worktrees (legacy naming)
│   ├── security/                  # → focus-groups/security branch
│   ├── onboarding/                # → focus-groups/onboarding branch
│   └── billing/                   # → focus-groups/billing branch
└── implementations/               # Implementation worktrees  
    ├── auth-v2/                   # → implementations/auth-v2 branch
    └── billing-api/               # → implementations/billing-api branch

Slack Integration

Channel Naming Convention:

• #{repo}-dev - Main development community channel
• #{repo}-{focus-group} - Focus group channels (e.g., #mvn-security)
• #{repo}-impl-{name} - Implementation channels (e.g., #mvn-impl-auth-v2)

Canvas Integration:

• Focus group ROADMAP.md ↔ Focus group channel canvas
• Implementation STATE.md ↔ Implementation channel canvas
• Master roadmap ↔ Main dev channel canvas

Canvas Creation Process: Canvas creation requires the exec tool with Slack API calls, not the message tool.

For Channel Canvases (recommended): Use conversations.canvases.create - creates canvas that appears as icon in channel automatically:

curl -X POST https://slack.com/api/conversations.canvases.create \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "channel_id": "CHANNEL_ID",
    "title": "Canvas Title",
    "document_content": {"type": "markdown", "markdown": "# Content"}
  }'

For Standalone Canvases: Use canvases.create + canvases.access.set (requires manual sharing):

# 1. Create standalone canvas
curl -X POST https://slack.com/api/canvases.create \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title": "Canvas Title", "document_content": {"type": "markdown", "markdown": "# Content"}}'

# 2. Share to channel
curl -X POST https://slack.com/api/canvases.access.set \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"canvas_id": "CANVAS_ID", "access_level": "read", "channel_ids": ["CHANNEL_ID"]}'

The Slack bot token is available in OpenClaw config: channels.slack.botToken

Versioning Strategy

Focus Groups & Concepts: No versions, just states

• [Draft] → [Exploring] → [Mature] → [Ready for Implementation]

Implementations: Semantic versioning based on merge reality

• Independent version planning: v2.1.0-auth-rework, v1.8.0-onboarding
• Actual version determined at merge time based on develop state
• Parallel implementations don't conflict because versions are contextual

Workflow Files

Located in workflows/:

• create-focus-group.md - Create focus group structure and channels
• create-concept.md - Add concept to focus group
• promote-concept.md - Move concept to implementation queue
• create-implementation.md - Start implementation from concept
• sync-canvas.md - Pull Slack canvas changes to git
• update-canvas.md - Push git changes to Slack canvas
• roadmap.md - Generate cross-focus-group status
• setup-repo.md - Initialize WGSD in repository

Success Criteria

• [ ] Focus groups can be created with channels and planning structure
• [ ] Concepts mature through social discussion in dedicated channels
• [ ] Ready concepts promote to controlled implementation (2-4 max)
• [ ] Canvas integration syncs bidirectionally with git planning
• [ ] Cross-channel references work through shared .planning/
• [ ] Parallel implementations don't conflict (semantic versioning)
• [ ] Team collaboration enabled through clear workflow explanation

</architecture>

<success_criteria>

• Repository initialized with WGSD planning structure
• Focus groups created with channels, canvases, and git branches
• Concepts tracked and promoted through maturity states
• Implementation channels limited to 2-4 concurrent maximum
• Canvas sync enables live roadmap collaboration in Slack
• Master roadmap aggregates status across all focus groups
• Clear developer onboarding and workflow documentation
• Slack-native approvals via conversation (Phase 14)
• Rich approval prompts with visual progress indicators
• Discussion threads capture approval context
• Rejection feedback required with re-review workflow </success_criteria>