one-shot

Execute planning, implementation, review, QA, and ship stages for Git projects.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill one-shot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-shot
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/one-shot
Command: npx skills add https://github.com/jikig-ai/soleur --skill one-shot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end engineering workflows by coordinating planning, deepening plans, implementing work, performing reviews, QA, and shipping from a single trigger.

Core Features & Use Cases

  • End-to-end orchestration: plan, deepen-plan, work, review, qa, compound, and ship phases with guardrails.
  • Branch isolation and PR automation: creates feature worktrees, draft PRs, and coordinates agents to avoid conflicts.
  • Robust failure handling: persists plan state, supports fallback paths, and resumes processing in real-world projects.

Quick Start

Run the one-shot skill to execute the full autonomous engineering workflow from plan to merged PR.

Frequently Asked Questions about one-shot

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

FAQPage Schema
How do I automate end-to-end engineering workflows from planning to PR?

Automating end-to-end engineering workflows involves executing plan, deepen-plan, work, review, QA, and ship phases sequentially. This process handles task sequencing, creates feature branches, and coordinates draft PRs autonomously.

Can I automate draft PR creation and feature branch isolation in Git?

Automating draft PR creation and feature branch isolation in Git is achieved by creating feature worktrees. This mechanism isolates changes and coordinates agents to prevent branch conflicts.

What is the best way to sequence software engineering tasks like QA and review?

Sequencing software engineering tasks like QA and review requires a structured orchestration pipeline with guardrails. The workflow progresses through distinct phases, ensuring each stage completes before the next begins.

Does autonomous engineering workflow orchestration support resuming after failures?

Autonomous engineering workflow orchestration supports resuming after failures by persisting plan state and providing fallback paths. This approach ensures processing resumes correctly in real-world projects.

When do I need orchestration guardrails for autonomous code shipping?

Orchestration guardrails for autonomous code shipping are needed when executing complex end-to-end workflows. They ensure robust failure handling, maintain state persistence, and coordinate multiple agents safely.