swe-orchestrator

Orchestrate software engineering skills for feature development workflows.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/MmtBkn/swe --skill swe-orchestrator-mmtbkn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-orchestrator
Source: https://github.com/MmtBkn/swe/tree/main/.cursor/skills/swe-orchestrator
Command: npx skills add https://github.com/MmtBkn/swe --skill swe-orchestrator-mmtbkn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the entire software development lifecycle, from initial context building to final code execution, ensuring a cohesive and efficient feature delivery process.

Core Features & Use Cases

  • Orchestrates SWE Skills: Manages the sequential execution of swe-init, swe-prd, swe-spec, swe-tdd, and swe-exec.
  • Handles Small Requests: Implements a distinct, streamlined workflow for single-story changes.
  • Use Case: Kick off a new feature request by having the orchestrator build initial context, generate a PRD, create a tech spec and test plan in parallel, and then execute the implementation, all managed through a single skill.

Quick Start

Use the swe-orchestrator skill to build a new feature following the full development workflow.

Frequently Asked Questions about swe-orchestrator

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

FAQPage Schema
How do I automate end-to-end feature development from context building to code execution?

End-to-end feature development automation orchestrates context initialization, PRD definition, technical specification, TDD, and sequential code execution into a cohesive workflow. It streamlines the entire lifecycle from initial request to final implementation.

What is the best way to manage a full software development workflow for a new feature?

Managing a full software development workflow requires orchestrating sequential phases: context initialization, product requirement definition, parallel technical specification and test-driven development, followed by sequential code execution for cohesive delivery.

Can I use workflow orchestration for single-story implementations instead of full feature development?

Workflow orchestration supports single-story implementations through a distinct, streamlined workflow. It dynamically manages both full feature development cycles and small, isolated changes based on the complexity of the incoming request.

Does test-driven development run sequentially or parallel with technical specification in feature development?

Test-driven development runs in parallel with technical specification during feature development. The orchestrator manages this concurrent execution before moving to the sequential code execution phase, ensuring specs and tests align simultaneously.

Do I need to manually initialize context before starting feature development orchestration?

Manual context initialization is not required before feature development orchestration. The orchestrator automatically builds the initial context as the first step, adhering to global rules for context persistence and fact-finding before defining product requirements.

When should I not use a full orchestrated workflow for software development?

A full orchestrated workflow should not be used for small or isolated change requests. For single-story implementations, the orchestrator bypasses the full lifecycle and applies a streamlined workflow tailored to low-complexity tasks.