npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

claude-symphony

v1.2.0

Published

One command. Production-grade software. From idea to deployment, automatically.

Readme

claude-symphony

Structured AI development. 8 stages. Quality gates. Checkpoints.

npm version License: MIT

What is claude-symphony?

Describe your app. claude-symphony runs an 8-stage AI pipeline — from brainstorming to deployment — producing a tested, deployable codebase with quality gates at every step.

npx claude-symphony init
# > "What do you want to build?"
# > "A real-time team collaboration tool with chat, file sharing, and video calls"
# > Pipeline starts automatically → 8 stages → tested, deployable codebase

How It Works

claude-symphony orchestrates an 8-stage pipeline where AI agents execute each stage:

| # | Stage | What happens | |---|-------|-------------| | 01 | Brainstorm | Generate features, user stories, requirements | | 02 | Research | Evaluate tech options, analyze feasibility | | 03 | Planning | Design architecture, data models, API, conventions | | 04 | UI/UX | Create wireframes, component tree, design tokens | | 05 | Tasks | Decompose into implementable tasks with priorities | | 06 | Implementation | TDD workflow + integrated refactoring + E2E sheet | | 07 | QA | Security audit, accessibility, full test execution | | 08 | Deployment | CI/CD pipeline, hosting, production deploy |

Multi-agent debate: Stages can run multiple Claude agents with different perspectives (e.g., Visionary vs Skeptic). This is a prompt-based protocol — agents are instructed to critique and refine each other's outputs within the conversation.

Each stage:

  • Includes role-specific instructions (creative for brainstorming, precise for implementation)
  • Validates outputs before progressing (quality gates)
  • Generates a HANDOFF document passing context to the next stage
  • Can be retried automatically if validation fails

Quality Gates

Every stage validates its outputs. Stage 06 (Implementation) guides a Write-Test-Verify workflow for each feature:

For EACH feature:
  1. Write tests first (unit + integration)
  2. Write implementation code
  3. Run tests → must pass before moving to next feature
  4. If tests fail → fix implementation, re-run

Quality gate (4 levels, must pass to complete):

| Level | Check | Required | |-------|-------|----------| | 1 | npm run build | Yes | | 2 | npm test — all tests pass | Yes | | 3 | npm run test:e2e — E2E tests | If configured | | 4 | Lint + typecheck | Recommended |

If validation fails, the stage retries with failure details injected into the prompt.

Quick Start

# Install and create a project
npx claude-symphony init

# Enter your Claude Code session
cd my-project
claude

# Start the auto-pilot pipeline
/auto-pilot

That's it. The pipeline runs through all 8 stages automatically.

See Getting Started for more details. You can also drop reference files into references/<stage>/ to give the AI additional context.

Commands

Inside Claude Code, you have 10 commands:

| Command | Description | |---------|-------------| | /auto-pilot | Start automatic pipeline execution | | /pause | Pause the pipeline after current stage | | /resume-stage | Resume a paused pipeline | | /skip | Skip the current stage | | /progress | View current pipeline progress | | /checkpoint | Create a save point | | /restore | Restore from a save point | | /stages | List all stages with status | | /run-stage [id] | Run a specific stage manually | | /debate | Run multi-agent debate for current stage |

CLI Commands

claude-symphony init              # Create new project
claude-symphony init --auto       # Create and auto-start
claude-symphony import ./my-app   # Import existing project
claude-symphony import ./my-app --dry-run  # Analyze without modifying
claude-symphony status            # Show pipeline status
claude-symphony stages            # List all stages
claude-symphony checkpoint        # Create checkpoint
claude-symphony restore [id]      # Restore from checkpoint

Import Existing Projects

Already have a project? Import it and run only the remaining stages:

claude-symphony import ./existing-app
# Analyzes your project → detects tests, CI/CD, components, etc.
# Skips completed stages → runs only what's missing

This is useful for taking an existing prototype and running it through QA, Testing, and Deployment.

Without vs With claude-symphony

| | Without | With claude-symphony | |---|---|---| | Output | Code (quality varies) | Tested codebase with CI/CD config | | Process | Manual or single generation | 10-stage pipeline with checkpoints | | Quality gates | None | 4-level verification (build, test, E2E, lint) | | Tests | Manual setup | Generated per feature | | Context management | Token window only | HANDOFF system between stages |

Documentation

Prerequisites

  • Claude Code installed and authenticated
  • Node.js >= 20.12.0

Contributing

git clone https://github.com/znehraks/claude-symphony.git
cd claude-symphony
pnpm install
pnpm run build
pnpm run test

See CLAUDE.md for development instructions.

License

MIT