oneshot_plan

Name: oneshot_plan
Availability: InStock
Author: Visuality

Execute a predefined development plan and implementation for a ticket.

4|Updated Jan 15, 2026

Search Tags:#automation #implementation #plan #ticket #ralph

Ready to run

npx skills add https://github.com/visualitypl/visuality-humanlayer --skill oneshot-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oneshot_plan
Source: https://github.com/visualitypl/visuality-humanlayer/tree/main/.github/skills/oneshot_plan
Command: npx skills add https://github.com/visualitypl/visuality-humanlayer --skill oneshot-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the execution of a plan and its subsequent implementation for a given ticket, streamlining the development workflow.

Core Features & Use Cases

Automated Plan Execution: Directly calls the /ralph_plan command to generate or retrieve a plan.
Automated Implementation: Follows up by calling the /ralph_impl command to execute the plan.
Use Case: When a new ticket is assigned that requires a predefined plan and implementation, this Skill can be invoked to quickly initiate both processes without manual intervention.

Quick Start

Use the oneshot_plan skill to execute the plan and implementation for ticket TICKET-123.

Frequently Asked Questions about oneshot_plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate ticket plan and implementation execution sequentially?▼

Automating ticket plan and implementation execution requires sequentially calling `/ralph_plan` and `/ralph_impl`. This process targets a specific ticket by taking its number as input to generate the plan and execute the implementation automatically without manual intervention.

What is the Ralph plan and implementation workflow for development tickets?▼

The Ralph plan and implementation workflow is an automated process that generates a predefined development plan and immediately executes its implementation for a specific ticket, streamlining the transition from planning to coding.

Do I need a specific ticket number to run the automated plan execution?▼

Yes, you need a specific ticket number to run the automated plan execution. The ticket number is a required input parameter that targets the correct task, ensuring both `/ralph_plan` and `/ralph_impl` execute for the right work item.

Can I use this to run ralph_plan and ralph_impl without manual intervention?▼

Yes, you can run `/ralph_plan` and `/ralph_impl` without manual intervention. The automation sequentially invokes both slash commands in a single operation, eliminating the need to trigger them separately during the development workflow.

What are the limitations of automating ticket implementation with predefined plans?▼

Automating ticket implementation with predefined plans is limited to executing existing `/ralph_plan` and `/ralph_impl` workflows sequentially. It does not support customizing the implementation logic or handling tickets that lack a predefined plan structure.