polly

Orchestrate NONoise project SDLC by asking questions and delegating to specialized skills.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill polly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polly
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/polly
Command: npx skills add https://github.com/russosalv/NONoise --skill polly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Polly removes uncertainty and context-switching when a team faces a newly scaffolded or existing NONoise project by guiding them step-by-step through the full software development lifecycle and engaging the right specialist skills at the right time. Instead of leaving users to guess which skill to run or what to do next, Polly asks the right questions, decides greenfield versus brownfield, and orchestrates requirements, design, architecture, sprint planning, and implementation handoffs.

Core Features & Use Cases

  • Guided decision tree: Asks a small number of focused questions (greenfield vs brownfield, stack, existing materials) and proceeds one step at a time.
  • Skill orchestration: Invokes bundled skills (requirements-ingest, bmad-agent-analyst, arch-brainstorm, arch-decision, sprint-manifest, superpowers dev trio, atr) or uses fallback templates when a skill is missing.
  • Workspace awareness: Detects multi-repo workspaces, explains repository scripts, and supports an auto-trigger flow via .nonoise/POLLY_START.md that self-destructs after the session.
  • Tool-specific behavior: Tailors mechanics for Claude Code (slash command and Skill tool invocation) and GitHub Copilot (reads SKILL.md files), and offers voice input guidance when helpful.
  • Use case: A developer opens a freshly scaffolded NONoise project and types /polly to be guided through requirements ingestion, architecture decisions, and sprint manifest creation without having to remember which skill to run next.

Quick Start

Type /polly or say start polly to begin an interactive SDLC orchestration and follow Polly's guided prompts.

Frequently Asked Questions about polly

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

FAQPage Schema
How do I orchestrate an AI-driven SDLC workflow across multiple specialized skills?

You can orchestrate an AI-driven SDLC workflow by using an orchestrator skill that asks clarifying questions and delegates tasks to specialized skills for requirements ingestion, architecture decisions, and sprint planning. Polly acts as this conductor, guiding you step-by-step without producing production code directly.

What's the best way to guide a development team through a newly scaffolded project lifecycle?

To guide a team through a newly scaffolded project, use a guided decision tree that determines greenfield versus brownfield status and detects multi-repo workspaces. Polly asks focused questions about your stack and existing materials, then invokes the right specialist skills at each stage.

Does SDLC orchestration work with both Claude Code and GitHub Copilot sessions?

Yes, SDLC orchestration works with both Claude Code and GitHub Copilot sessions. The orchestrator tailors its mechanics for Claude Code via slash commands and Skill tool invocation, and for GitHub Copilot by reading SKILL.md files directly.

How do I start an automated software development lifecycle workflow in my repository?

You can start an automated SDLC workflow by typing /polly or saying start polly to begin interactive orchestration. Alternatively, add a .nonoise/POLLY_START.md file to your repository to auto-trigger the session, which self-destructs after completion.

What happens if a required specialist skill is missing during SDLC orchestration?

If a required specialist skill is missing during SDLC orchestration, the orchestrator falls back to manual templates to keep the workflow moving. Polly requires bundled skills for full functionality but provides fallback options for scenarios where specific skills are unavailable.

Can I use SDLC orchestration for multi-repo workspace environments?

Yes, you can use SDLC orchestration for multi-repo workspaces. The orchestrator detects multi-repo environments, explains repository scripts, and guides development across the full software development lifecycle while maintaining awareness of your workspace structure.