founder-os: Command for Claude Code

Create Command Wizard

Interactively create a new slash command for your founder-os instance.

Arguments

• $ARGUMENTS - (Optional) Name or description of the command to create

Process

Step 1: Command Identity

Ask the user (or derive from arguments):

• Command name: What should the command be called? (e.g., deploy, audit, sprint-plan)
• Category: Where should it live?

Use AskUserQuestion:

• Question: "What category should this command belong to?"
• Options:
  • "queue" - Work queue management
  • "founder" - Founder tools
  • "team" - Team management
  • "config" - Configuration
  • (Other will be entered manually)

The command file will be created at .claude/commands/{category}/{name}.md.

Step 2: Command Purpose

Ask: "What should this command do? Describe in 1-2 sentences."

Record as the description in the frontmatter.

Step 3: Tool Requirements

Use AskUserQuestion with multiSelect:

• Question: "What tools does this command need access to?"
• Options:
  • "Read" - Read files from the filesystem
  • "Write, Edit" - Create and modify files
  • "Bash" - Run shell commands
  • "Task, Glob, Grep" - Search codebase and spawn subagents
  • "AskUserQuestion" - Interactive prompts to the user

Step 4: Agent Assignment

Use AskUserQuestion:

• Question: "Which agent type should primarily use this command?"
• Options:
  • "Any agent" - No specific owner
  • "staff-software-architect" - Architecture and design
  • "staff-product-manager" - Product decisions
  • "staff-engineer" - Implementation

Step 5: Generate Command

Create the command file with this structure:

---
description: {description from step 2}
allowed-tools: {tools from step 3}
---

# {Command Title}

{Description of what this command does.}

## Arguments

- `$ARGUMENTS` - {describe expected arguments}

## Process

1. {Step 1 - what to do first}

2. {Step 2 - main action}

3. {Step 3 - verification/output}

## Output

{Describe what the command reports when done}