polly

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.