jvoliveiran

Constellation Harness — AI skill for Claude Code

AI community

Constellation Harness — multi-agent software delivery workflow for Claude Code (orchestrator, persona agents, quality gates, cross-model validation).

How to install Constellation Harness

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jvoliveiran/constellation-harness and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Constellation Harness does

Constellation Harness — multi-agent software delivery workflow for Claude Code (orchestrator, persona agents, quality gates, cross-model validation).

Alternatives in AI

  • Develop — Development phase - Build solutions with multi-AI implementation and quality gates 2.8k ★
  • Loushang — AI-native agent harness for coding workflows by python: multi-model LLM orchestration, stateful sessions, tool 1.3k ★
  • Pilotfish — Multi-model orchestration layer for Claude Code — the frontier model plans, cheaper models execute, verificati 688 ★

README

Constellation Harness

A multi-agent software delivery workflow for [Claude Code](https://code.claude.com), packaged as plugins. An orchestrator classifies every request, routes it through specialist persona agents (architect → engineer → parallel reviewers → SDET/writer → devops), and enforces quality gates, workflow state, and review memory along the way.

Extracted from a markdown-based `.agentic` workflow system and reworked to use native Claude Code plugin primitives: subagents, skills, commands, and hooks.


Repository Layout

constellation-harness/                 (plugin marketplace)
├── .claude-plugin/marketplace.json
└── plugins/
    ├── constellation/                 CORE — universal harness
    │   ├── agents/                    11 persona subagents
    │   ├── commands/                  /constellation:* workflow commands
    │   ├── skills/                    orchestrator + generic delivery skills
    │   ├── templates/                 files scaffolded by /constellation:init
    │   ├── hooks/ + scripts/          SessionStart activation (gated per project)
    │   └── .claude-plugin/plugin.json
    ├── constellation-stack-node/      OPT-IN — Node/NestJS/GraphQL/Prisma skills
    │   ├── skills/
    │   └── .claude-plugin/plugin.json
    ├── constellation-stack-frontend/  OPT-IN — frontend design skills
    │   ├── skills/
    │   └── .claude-plugin/plugin.json
    ├── constellation-stack-service/   OPT-IN — constellation-service boilerplate recipes
    │   ├── skills/                    (layers on top of constellation-stack-node)
    │   └── .claude-plugin/plugin.json
    └── constellation-stack-infra/     OPT-IN — cloud infrastructure (Terraform, OCI/AWS)
        ├── agents/                    cloud-architect persona subagent
        ├── skills/
        └── .claude-plugin/plugin.json

Installation

The mental model: **install once per machine, then enable + init once per repo.** Installing a plugin only makes it *available* — i