One-Shot Research & Plan

Research and plan ticket: $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 - Ticket Number (required)

Specify ticket to research and plan:

• Ticket number: "ENG-1234" or "1234"
• With context: "Complete research and planning for ENG-1234"

Default Behavior

Requires ticket number. Executes sequential workflow:

1. /ralph-research - Research ticket and gather context
2. Launch planning session with Opus model and 14-minute timeout

Usage

# Research and plan a Linear ticket
/oneshot ENG-1234

# With context
/oneshot "Complete research and planning for ENG-1234"

Implementation

1. Use SlashCommand() to call /ralph-research with the given ticket number
2. Launch a new session with npx humanlayer launch --model opus --dangerously-skip-permissions --dangerously-skip-permissions-timeout 14m --title "plan ENG-XXXX" "/oneshot-plan ENG-XXXX"

---

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 oneshot completes:

✅ COMMAND COMPLETE: /oneshot
Ticket: <ticket-id>
Research: Complete
Session: Launched
Plan: In progress

Completion Checklist

Before marking complete:

• Ticket fetched
• Research done
• Planning session launched
• Opus model activated

Failure Indicators

This command has FAILED if:

• ❌ No ticket provided
• ❌ Ticket not found
• ❌ Research failed
• ❌ Session not launched

When NOT to Use

Do NOT use when:

• Already have plan (use /oneshot-plan)
• No ticket exists
• Quick fix sufficient

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Skip research	Missing context	Let research complete
Wrong model	Lower quality	Use Opus for planning
Timeout too short	Incomplete plan	Use adequate timeout

Principles

This command embodies:

• #3 Complete Execution - Full research-plan workflow
• #9 Based on Facts - Ticket-based work
• #6 Clear, Understandable - Clear progression

Full Standard: CODITECT-STANDARD-AUTOMATION.md