polisade

Polisade Orchestrator

Autonomous Development Framework — part of the Polisade toolchain.

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

Detailed usage guide: 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 + three distribution zips. Feedback via Discussions. Issues are disabled by design — see CONTRIBUTING.md.

Contents

• Why Polisade Orchestrator?
• Installation
• Quick Start
• Detailed Guide
• Natural Language
• Three Work Levels
• Command Reference
• Autonomous Cycle
• Architecture
• Release Notes
• Repository Layout
• Contributing
• License

Why Polisade Orchestrator?

• From idea to merged PR, hands-off. Claude drives the full loop — plan, implement, test, PR, review, merge — while the PM stays in the loop only for real decisions.
• Doc-as-code, first-class. PRD, SPEC, DESIGN (C4/ERD/OpenAPI), ADR and glossary live in the repo as traceable artifacts linked to every FR/NFR.
• Independent quality loop. PR review is done by an external reviewer (Codex CLI by default, or the current agent's CLI with self flag) — ensuring independent second opinion.

Installation

Polisade Orchestrator ships three parallel releases on every git tag — pick the one that matches the CLI you use. All three expose the same /polisade:* slash commands.

Claude Code

# 1. Add marketplace (once per machine)
/plugin marketplace add cryndoc/polisade-orchestrator

# 2. Install plugin into your project
/plugin install polisade --scope project

# 3. Initialize Polisade Orchestrator structure in your project
/polisade:init MyProjectName

Qwen CLI

# 1. Download the latest Qwen extension release
mkdir -p ~/.qwen/extensions
curl -sL https://github.com/cryndoc/polisade-orchestrator/releases/latest/download/polisade-qwen.zip \
  | bsdtar -xvf - -C ~/.qwen/extensions/

# 2. Launch Qwen — /polisade:* commands are auto-registered
qwen

# 3. Initialize Polisade Orchestrator structure inside your project
/polisade:init MyProjectName

Non-interactive mode. Interactive REPL (qwen without args) approves shell calls inline. For scripted use with -p '/polisade:<cmd>', bypass the approval gate:

qwen --allowed-tools=run_shell_command -p '/polisade:review-pr 21'

The CLI's own hint — --approval-mode=auto-edit — is misleading: it covers edit tools (WriteFile, Edit) only, not shell.

GigaCode CLI (corporate Qwen fork)

# 1. Download the latest GigaCode extension release
mkdir -p ~/.gigacode/extensions
curl -sL https://github.com/cryndoc/polisade-orchestrator/releases/latest/download/polisade-gigacode.zip \
  | bsdtar -xvf - -C ~/.gigacode/extensions/

# 2. Launch GigaCode — /polisade:* commands are auto-registered
gigacode

# 3. Initialize Polisade Orchestrator structure inside your project
/polisade:init MyProjectName

Non-interactive mode. Interactive REPL (gigacode without args) approves shell calls inline. For scripted use with -p '/polisade:<cmd>', bypass the approval gate:

gigacode --allowed-tools=run_shell_command -p '/polisade:review-pr 21'

The CLI's own hint — --approval-mode=auto-edit — is misleading: it covers edit tools (WriteFile, Edit) only, not shell.