skills.rest
lvlup-sw
lvlup-swOFFICIAL
Explore all skills by this author →
GitHub

oneshot-workflow

Coordinate small code changes through an auditable four-phase workflow.

33|Updated Jan 5, 2026
Search Tags:#workflow#tdd#audit#synthesis#pr#guard#oneshot
One-click install
npx skills add https://github.com/lvlup-sw/exarchos --skill oneshot-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oneshot-workflow
Source: https://github.com/lvlup-sw/exarchos/tree/main/skills-src/oneshot-workflow
Command: npx skills add https://github.com/lvlup-sw/exarchos --skill oneshot-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing small, bounded changes safely without losing context between sessions or manual notes.

Core Features & Use Cases

  • Four-phase, auditable workflow: plan, implementing, synthesize, completed.
  • Optional PR path via synthesisPolicy or runtime synthesize request, plus TDD discipline.
  • No subagent dispatch required for straightforward changes; end-to-end traceability.

Quick Start

Initiate a oneshot workflow for a small change and complete the four phases.

Frequently Asked Questions about oneshot-workflow

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

FAQPage Schema
How do I manage small code changes with an auditable workflow?▼

TDD is enforced as the build discipline during the implementing phase. The workflow requires a synthesisPolicy or a synthesize-request signal to determine whether your code changes follow a direct-commit path or a PR path.

Can I use this workflow for complex multi-file edits requiring subagent dispatch?▼

No, this workflow applies to trivial fixes, config tweaks, and single-file edits where subagent dispatch and multi-stage reviews are unnecessary. Complex changes require a different workflow approach.

How do I choose between a direct-commit and a PR path for config tweaks?▼

The path is chosen by providing a synthesisPolicy or a runtime synthesize-request signal. This determines whether your config tweaks are committed directly or routed through a PR for review.

What is the best way to ensure traceability for single-file edits without manual notes?▼

The best way to ensure traceability is running the four-phase workflow: plan, implementing, synthesize, completed. It maintains context across sessions automatically, eliminating the need for manual notes during single-file edits.

Do I need to set up dependencies to run the four-phase workflow?▼

No dependencies are required to run the four-phase workflow. You can initiate the workflow immediately for your small changes and complete the plan, implementing, synthesize, and completed phases without external setup.

Related Skills

Explore More Software Engineering Skills→
buchananwillbuchananwill
2

tdd-implementation-io-schema

Define structured input/output contracts for TDD code implementation reports.

Community
Intermediate
friedbotstudiofriedbotstudio
5

chore

Standardize non-TDD chore edits with mandatory archive, memory-flush, and commit steps.

Official
Advanced
bjornjeebjornjee
19

implement

Dispatch pending plan phases to TDD-enforced subagent workflows with validation.

Community
Advanced
ovargasovargas
12

subagent-driven-development

Orchestrate per-task subagents with wave-based dispatch and two-stage review gates.

Community
Advanced