twig-sdlc

Orchestrates end-to-end SDLC pipeline for twig development from planning to close-out.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/PolyphonyRequiem/polyphony --skill twig-sdlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twig-sdlc
Source: https://github.com/PolyphonyRequiem/polyphony/tree/main/.github/skills/twig-sdlc
Command: npx skills add https://github.com/PolyphonyRequiem/polyphony --skill twig-sdlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive, error-prone effort of coordinating an end-to-end SDLC process by routing an Azure DevOps work item (or a prompt) through planning, implementation, PR lifecycle, and close-out using deterministic workflow logic.

Core Features & Use Cases

  • End-to-end SDLC orchestration: Drives planning through review gates, seeds child Issues/Tasks, manages branch/PR lifecycle, and completes close-out in one long-running Conductor run.
  • Type-agnostic routing for ADO work items: Handles Epic/Issue/Task hierarchies without hardcoded process-template assumptions by relying on configuration-driven routing.
  • Operational guardrails for reliability: Requires a dedicated worktree, recommends detached hidden execution, and enforces input parameters needed for GitHub PR targeting.

Quick Start

Ask the workflow to run the full SDLC for your ADO work item by activating twig-sdlc with your work_item_id and GitHub PR target inputs (pr_owner, pr_repo_name, and gh_user) and starting it with the Conductor web dashboard.

Frequently Asked Questions about twig-sdlc

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

FAQPage Schema
How do I orchestrate an end-to-end SDLC pipeline for Azure DevOps work items?

End-to-end SDLC pipeline orchestration for Azure DevOps work items is handled by routing planning, implementation, PR lifecycle, and close-out phases through deterministic workflow logic. It manages Epic, Issue, and Task hierarchies using configuration-driven routing.

How do I automate GitHub pull request creation and review for Azure DevOps tasks?

Automating GitHub pull request creation and review for Azure DevOps tasks requires providing mandatory PR target parameters including pr_owner, pr_repo_name, and gh_user. The workflow then manages the full PR lifecycle alongside implementation and close-out.

What is needed to start an automated workflow for SDLC planning and pull request handling?

Starting an automated workflow for SDLC planning and pull request handling requires a dedicated worktree and mandatory GitHub PR target inputs. Execution should be initiated via the Conductor web dashboard using your work_item_id and GitHub parameters.

Can I resume or redo an interrupted SDLC workflow orchestration run?

Resuming or redoing an interrupted SDLC workflow orchestration run is fully supported through intent-based execution. The deterministic Conductor workflow allows users to resume from an existing plan, redo actions, or resume interrupted operations.

Does end-to-end SDLC orchestration support recursive planning for composite routing scenarios?

End-to-end SDLC orchestration supports full composite routing scenarios including recursive planning. It seeds work-tree structures into child Issues and Tasks, driving the entire process from planning through review gates to final close-out filing.