polyphony-bootstrap

Bootstrap repositories into the Polyphony SDLC engine with configuration and smoke tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Polyphony-bootstrap prevents broken SDLC routing and configuration wiring by providing a guided, prerequisite-checked onboarding path for repos that have twig and the polyphony CLI installed but are missing the initial .polyphony-config/ directory.

Core Features & Use Cases

  • Prerequisite verification: Confirms the expected polyphony CLI verbs and that twig workspace discovery works before any configuration authoring starts.
  • End-to-end smoke testing: Runs a six-step command sequence to validate-config, confirm hierarchy/type mapping, compute next-ready routing, validate transitions, and ensure the target state exists in twig without writing to ADO.
  • Bootstrap pitfall catalog + checklist: Identifies common configuration and vocabulary mismatches (including scope_removed pitfalls, facet validation issues, and config argument-shape errors) and provides an operator-ready checklist for readiness.
  • Guided onboarding flow: Points to the long-form docs for full walkthrough while supplying the missing agent-loadable operational steps.

Quick Start

Run this skill’s prerequisite checks and smoke test against one real work item ID after generating .polyphony-config/ from your chosen process template.

Frequently Asked Questions about polyphony-bootstrap

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

FAQPage Schema
How do I validate Azure DevOps SDLC routing before running workflows?

You can validate Azure DevOps SDLC routing by running a deterministic smoke test that checks configuration validation, hierarchy mapping, and state transitions without writing to ADO. This proves your workflow wiring is correct before execution.

What is needed to bootstrap a repository into the Polyphony SDLC engine?

Bootstrapping a repository requires the twig workspace tool and the polyphony CLI installed, but operates when the .polyphony-config/ directory is missing. The process scaffolds the required configuration from your chosen process template.

How do I run a CLI smoke test for Agile or Scrum process template onboarding?

Run a six-step CLI smoke test sequence using polyphony validate-config, hierarchy, state next-ready, and validate commands. This verifies type resolution, routing, and transition correctness against a real work item ID.

Why does state transition validation fail when wiring a new SDLC configuration?

State transition validation fails due to common configuration and vocabulary mismatches, including scope_removed pitfalls, facet validation issues, and config argument-shape errors. An operator-ready checklist helps identify and resolve these specific bootstrap pitfalls.

Can I verify twig process DRY state-name resolution without executing a full workflow?

Yes, you can verify DRY state-name resolution using twig process before any workflow execution. This check ensures the target state exists in twig and confirms routing correctness without triggering actual workflow runs.

Do I need prerequisite verification before scaffolding the .polyphony-config/ directory?

Yes, prerequisite verification confirms expected polyphony CLI verbs and twig workspace discovery work before any configuration authoring starts. This prevents broken SDLC routing caused by missing operational dependencies.