full-orchestration

Reviews specs and plans for missing requirements, edge cases, and untested scenarios

Reviews specs and plans for performance bottlenecks, resource usage, and scalability

Converts a technical spec into a step-by-step implementation plan with file-level changes

Reviews specs and plans for long-term maintainability, readability, and code health

Reviews specs and plans for security vulnerabilities, unsafe patterns, and OWASP risks

Synthesizes codebase exploration findings into a detailed technical specification

Implements features using test-driven development on a feature branch

Implement a ticket using TDD and review in a converging loop. Use when you have an approved spec and implementation plan. Spawns TddEngineer for implementation, delegates to deep-review for adversarial analysis, and auto-fixes findings in an autonomous loop (max 5 rounds) before gating user approval.

Create a pull request from a reviewed implementation branch. Use when the implementation and review stage is approved and you are ready to open a PR. Generates a conventional-commit title, structured body with ticket link, spec summary, test results, and review findings, then creates the PR via gh CLI.

Run a four-agent review on a technical spec or implementation plan. Use when a spec or plan needs evaluation from maintainability, security, efficiency, and completeness perspectives. Spawns four reviewer agents that write structured comment files, then merges all comments into the document in a single conflict-free pass.

Generate a technical spec and implementation plan for a ticket. Use when you have parsed requirements and need a detailed design before implementation. Orchestrates codebase exploration, spec authoring, autonomous review-fix loops, implementation planning, and plan review-fix loops across multiple agents.

Run the full software engineering pipeline from ticket to PR. Use when starting a feature, fixing a bug from a ticket, or driving end-to-end development from a Jira, Linear, or GitHub issue. Accepts a ticket ID or URL as argument and orchestrates intake, spec design, TDD implementation, code review, and PR creation with approval gates at each stage.

Show the current state of an /swe pipeline run. Use when checking pipeline progress, resuming after an interruption, or reviewing what stage a ticket has reached. Accepts a ticket ID or lists all active pipelines if no argument given.

Fetch and parse a ticket from Jira, Linear, or GitHub Issues. Use when starting work on a ticket, beginning a new feature, or when given a ticket ID or issue URL. Accepts a ticket ID or full URL as argument, auto-detects the ticketing system, and produces a structured requirements summary.