One-Shot Plan & Implement

Plan and implement: $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 process:

• Ticket number: "ENG-1234" or "1234"
• With context: "Complete workflow for ENG-1234"

Default Behavior

Requires ticket number. Executes sequential workflow:

1. /ralph-plan - Creates implementation plan for ticket
2. /ralph-impl - Implements the approved plan

Usage

# Plan and implement a ticket
/oneshot-plan ENG-1234

# With context
/oneshot-plan "Complete workflow for ENG-1234"

Implementation

1. Use SlashCommand() to call /ralph-plan with the given ticket number
2. Use SlashCommand() to call /ralph-impl with the given ticket number

---

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

✅ COMMAND COMPLETE: /oneshot-plan
Ticket: <ticket-id>
Plan: Created
Implementation: Complete
Tests: Passing
Status: Ready for review

Completion Checklist

Before marking complete:

• Ticket fetched
• Plan created
• Implementation done
• Tests passing
• Changes committed

Failure Indicators

This command has FAILED if:

• ❌ No ticket provided
• ❌ Ticket not found
• ❌ Plan failed
• ❌ Implementation failed

When NOT to Use

Do NOT use when:

• Need research first (use /oneshot)
• Manual review required
• Complex multi-ticket work

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Skip tests	Bugs	Always run tests
Force implementation	Wrong approach	Let plan complete
Skip review	Quality issues	Review before merge

Principles

This command embodies:

• #3 Complete Execution - Full plan-to-impl
• #9 Based on Facts - Ticket-based work
• #6 Clear, Understandable - Clear status

Full Standard: CODITECT-STANDARD-AUTOMATION.md