cryndoc/polisade-orchestrator

6 stars · Last commit 2026-08-14

Autonomous development framework for Claude Code, Qwen CLI, GigaCode CLI and opencode — /polisade:* commands drive the full cycle: spec → tasks → implement → review → merge. Read-only release mirror.

README preview

# Polisade Orchestrator

**Autonomous Development Framework** — part of the **Polisade** toolchain.

[![Latest release](https://img.shields.io/github/v/release/cryndoc/polisade-orchestrator?label=release)](https://github.com/cryndoc/polisade-orchestrator/releases/latest)
[![License](https://img.shields.io/badge/license-Apache%202.0-green)](LICENSE)
[![Claude Code](https://img.shields.io/badge/Claude%20Code-plugin-6E57FF)](https://claude.com/claude-code)

Claude operates as a full dev team: **implement → test → PR → review → merge**. PM interacts through natural language or slash commands. The plugin ships under the technical id `polisade` and exposes its behavior as `/polisade:*` slash commands — those identifiers are intentionally kept stable for install-path and cache compatibility.

Release history: [RELEASE_NOTES.md](RELEASE_NOTES.md)

Detailed usage guide: [docs/framework-usage-guide.md](docs/framework-usage-guide.md)

> **Note.** This repository is a read-only release snapshot. Each release is a single orphan commit with the source tree + four distribution zips. Bug reports and feature requests via [Issues](https://github.com/cryndoc/polisade-orchestrator/issues), questions via [Discussions](https://github.com/cryndoc/polisade-orchestrator/discussions) — see [CONTRIBUTING.md](CONTRIBUTING.md). Pull requests are not accepted here (development happens in a separate private repository).

## Contents

- [Why Polisade Orchestrator?](#why-polisade-orchestrator)
- [Installation](#installation)

View full repository on GitHub →