full-orchestration

Plugin full-orchestration from marketplace ghcp-dev-plugins in shouenlee/ghcp-dev-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• implement_and_review

  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

• pr_create

  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 C

• spec_review

  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 sin

• spec_writer

  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 a

• swe

  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,

• swe_status

  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.

• ticket_intake

  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.

Subagents (7)

• CompletenessReviewer

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

• EfficiencyReviewer

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

• ImplPlanner

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

• MaintainabilityReviewer

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

• SecurityReviewer

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

• SpecArchitect

  Synthesizes codebase exploration findings into a detailed technical specification

• TddEngineer

  Implements features using test-driven development on a feature branch

Similar plugins