swe-orchestrator

Orchestrate the full SDLC for feature development from GitHub issues.

Updated Feb 18, 2026

Search Tags:#automation #code review #feature development #orchestration #agile #sdlc

Ready to run

npx skills add https://github.com/diegocanepa/agent-skills --skill swe-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swe-orchestrator
Source: https://github.com/diegocanepa/agent-skills/tree/main/skills/swe-orchestrator
Command: npx skills add https://github.com/diegocanepa/agent-skills --skill swe-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires swe-architect, swe-planner, swe-implementer, swe-reviewer, vcs-issue-management, vcs-branch, vcs-commit, vcs-change-request, mermaid-diagrams, backend-coder, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire Software Development Lifecycle (SDLC) for a given feature, from initial architectural design to final code merge and issue closure, ensuring a streamlined and auditable development process.

Core Features & Use Cases

Full SDLC Orchestration: Manages architecture, planning, implementation, and review phases.
Automated Workflow: Integrates multiple specialized skills for a cohesive development pipeline.
Use Case: Kick off the development of a new user authentication module by providing a GitHub issue; the orchestrator will handle the architecture, task breakdown, coding, reviews, and merging.

Quick Start

Initiate the complete feature development process for the new user profile page by providing the GitHub issue details.

Frequently Asked Questions about swe-orchestrator

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

FAQPage Schema

How do I automate the full software development lifecycle for a new feature?▼

To automate the software development lifecycle for a new feature, you provide a GitHub issue to trigger an orchestration pipeline that manages architecture, task planning, iterative implementation, and code review before final merging.

What is the best way to orchestrate SDLC phases from architecture to code merge?▼

The best way to orchestrate SDLC phases is using an automation skill that coordinates specialized modules for architectural design, task breakdown, backend coding, and quality-gated reviews, ensuring an auditable path to code merge.

Can I trigger agile feature development directly from a GitHub issue?▼

Yes, you can trigger agile feature development directly from a GitHub issue, which the orchestrator uses to initiate architectural analysis, plan tasks via a `.plan/` file, and execute iterative implementation automatically.

Does the orchestrator enforce conventional commit standards during code review?▼

Yes, the orchestrator enforces conventional commit standards during the code review phase, ensuring that iterative implementation and subsequent merges adhere to defined quality gates and standard commit formatting.

Do I need specialized skills for task planning and architectural analysis to use this?▼

You do not need to manually invoke them; the orchestrator automatically integrates specialized skills like swe-architect, swe-planner, and swe-implementer to handle the complete feature development pipeline internally.

When should I not use an automated SDLC orchestration approach?▼

You should avoid automated SDLC orchestration for feature development if your project requires manual intervention for architectural analysis or if your workflow cannot integrate with conventional commit standards and `.plan/` file state persistence.