Founder Mode

Setup ticketing for: $ARGUMENTS

System Prompt

⚠️ EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

1. IMMEDIATELY execute - no questions, no explanations first
2. ALWAYS show full output from script/tool execution
3. ALWAYS provide summary after execution completes

DO NOT:

• Say "I don't need to take action" - you ALWAYS execute when invoked
• Ask for confirmation unless requires_confirmation: true in frontmatter
• Skip execution even if it seems redundant - run it anyway

The user invoking the command IS the confirmation.

---

Arguments

$ARGUMENTS - Commit Context (optional)

Specify the experimental commit to formalize:

• Auto-detect: No arguments - uses most recent commit
• Specific commit: "Setup PR for commit abc123"
• With description: "Formalize experimental auth feature commit"

Default Behavior

If no arguments:

• Detects most recent commit
• Creates Linear ticket retroactively
• Sets up proper git branch
• Creates PR with full description

Usage

# Auto-detect most recent commit
/founder-mode

# Specify commit context
/founder-mode "Setup PR for authentication feature"

# Formalize specific commit
/founder-mode "Formalize commit abc123 for user dashboard"

Example

# After making an experimental commit directly to main
/founder-mode "Retroactive PR for new logging system"

# Output:
# 1. Detected commit: abc1234 "feat: add logging system"
# 2. Created Linear ticket: CODI-456
# 3. Created branch: codi-456-logging-system
# 4. Cherry-picked commit to new branch
# 5. Created PR #78 with full description

---

You're working on an experimental feature that didn't get the proper ticketing and pr stuff set up.

Assuming you just made a commit, here are the next steps:

1. get the sha of the commit you just made (if you didn't make one, read .claude/commands/commit.md and make one)

2. read .claude/commands/linear.md - think deeply about what you just implemented, then create a linear ticket about what you just did, and put it in 'in dev' state - it should have ### headers for "problem to solve" and "proposed solution"

3. fetch the ticket to get the recommended git branch name

4. git checkout main

5. git checkout -b 'BRANCHNAME'

6. git cherry-pick 'COMMITHASH'

7. git push -u origin 'BRANCHNAME'

8. gh pr create --fill

9. read '.claude/commands/describe-pr.md' and follow the instructions

---

Action Policy

<default_behavior> This command implements changes by default when user intent is clear. Proceeds with:

• Code generation/modification
• File creation/updates
• Configuration changes
• Git operations (if applicable)

Provides concise progress updates during execution. </default_behavior>

After execution, verify: - Files created/modified as intended - Code compiles/tests pass (if applicable) - Git changes committed (if applicable) - Next recommended step provided

Success Output

When founder mode workflow completes:

✅ COMMAND COMPLETE: /founder-mode
Commit: <sha>
Ticket: CODI-<NNN>
Branch: <branch-name>
PR: #<number>
Description: Created

Completion Checklist

Before marking complete:

• Commit SHA identified
• Linear ticket created
• Branch created
• Cherry-pick successful
• PR created with description

Failure Indicators

This command has FAILED if:

• ❌ No commit to formalize
• ❌ Linear ticket creation failed
• ❌ Cherry-pick conflict
• ❌ PR creation failed

When NOT to Use

Do NOT use when:

• Already have proper branch/PR
• Commit already on feature branch
• No experimental commits to formalize

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Skip ticket	No tracking	Always create Linear ticket
Force push	Lost history	Use cherry-pick
Skip PR description	Poor documentation	Use /describe-pr

Principles

This command embodies:

• #3 Complete Execution - Full formalization workflow
• #9 Based on Facts - Retroactive documentation
• #6 Clear, Understandable - Proper ticket/PR flow

Full Standard: CODITECT-STANDARD-AUTOMATION.md