ΰΈ ΰΈ²ΰΈ©ΰΈ²ΰΉΰΈΰΈ’ / Thai: ΰΈΰΉΰΈ²ΰΈ README ΰΈ ΰΈ²ΰΈ©ΰΈ²ΰΉΰΈΰΈ’
π Presentation
[!NOTE] Governance for Claude Code β ship with confidence, not just speed. A structured multi-team AI governance framework that turns Claude Code into a coordinated engineering organization with specialized teams, approval gates, automated policy enforcement, and full audit trail.
By Unicorn Tech Integration Co., Ltd.
Table of Contents
- Why UniOps Quantum Cycle?
- Quick Start
- Three Ways to Use
- VSCode Extension
- Teams
- Skills
- Rules & Hooks
- Project Structure
- Policies
- Customization
- Requirements
π€ Why UniOps Quantum Cycle?
| ποΈ 5 Teams 16 specialized personas |
π Phase Gates Ticket-driven workflow |
π Full Audit Trail Every decision logged |
β‘ 21 Skills Ready-made slash commands |
π‘οΈ Policy Engine 9 enforced standards |
| Vanilla Claude Code | UniOps Quantum Cycle | |
|---|---|---|
| Structure | Single assistant | β 5 teams + 16 personas |
| Planning | π§ Ad hoc | β Phase dispatch + ticket gates |
| Code Review | π§ Manual | β 2-pass + cross-layer trace |
| Shipping | π§ Manual git | β
/git pr with rebase + governance gates |
| QA | π§ Manual | β Playwright MCP + smoke test gates |
| Retrospective | β None | β
/git lookback β git + session data + decision audit |
| Governance | β None | β Full hierarchy + approval gates |
| Audit Trail | β None | β Every decision logged + traceable |
| Multi-Team | β No | β 4 teams + parallel execution |
| Setup | β | β‘ ~30 seconds |
π Quick Start
Install via Claude Code (Recommended)
Copy and paste into Claude Code:
π¬π§ English:
Install UniOps Quantum Cycle from https://github.com/VarakornUnicornTech/UniOpsQC into my current project. Follow the Getting Started guide at https://github.com/VarakornUnicornTech/UniOpsQC/wiki/Getting-Started
πΉπ Thai / ΰΈ ΰΈ²ΰΈ©ΰΈ²ΰΉΰΈΰΈ’:
ΰΈΰΈ΄ΰΈΰΈΰΈ±ΰΉΰΈ UniOps Quantum Cycle ΰΈΰΈ²ΰΈ https://github.com/VarakornUnicornTech/UniOpsQC ΰΈ₯ΰΈΰΉΰΈ project ΰΈΰΈ±ΰΈΰΈΰΈΈΰΈΰΈ±ΰΈ ΰΈΰΈ²ΰΈ‘ Getting Started ΰΈΰΈ΅ΰΉ https://github.com/VarakornUnicornTech/UniOpsQC/wiki/Getting-Started
[!TIP] Use "install" β not "read" or "explain". Saying "install" makes Claude go straight to setup without reading every policy file first.
Manual Install
[!NOTE] Replace
C:/Projects/my-projectin the commands below with the actual path to your project folder β the folder where you want to install UniOps Quantum Cycle.
Bash / Git Bash / macOS / Linux:
git clone https://github.com/VarakornUnicornTech/UniOpsQC.git .claude-template
cp -r .claude-template/.claude/ C:/Projects/my-project/.claude/
cp .claude-template/template-version.json C:/Projects/my-project/template-version.json
cp .claude-template/plugin.json C:/Projects/my-project/plugin.json
cp .claude-template/.mcp.json C:/Projects/my-project/.mcp.json
cp -r .claude-template/hooks/ C:/Projects/my-project/hooks/
rm -rf .claude-template
PowerShell (Windows):
git clone https://github.com/VarakornUnicornTech/UniOpsQC.git .claude-template
Copy-Item -Recurse .claude-template\.claude\ C:\Projects\my-project\.claude\
Copy-Item .claude-template\template-version.json C:\Projects\my-project\template-version.json
Copy-Item .claude-template\plugin.json C:\Projects\my-project\plugin.json
Copy-Item .claude-template\.mcp.json C:\Projects\my-project\.mcp.json
Copy-Item -Recurse .claude-template\hooks\ C:\Projects\my-project\hooks\
Remove-Item -Recurse -Force .claude-template
[!TIP] After installing, edit
.claude/ProjectEnvironment.mdwith your project name and paths before starting Claude Code for the first time.
[!NOTE] Windows β Hook scripts require
jq: Install via winget (winget install jqlang.jq) or Chocolatey (choco install jq), then restart your terminal. Withoutjq, hook scripts will not function.Playwright MCP (optional): Required only if you want browser automation for UX smoke tests. Install Node.js and run
npx playwright installinside your project.
π― Three Ways to Use UniOps Quantum Cycle
[!TIP] Each level is fully opt-in. Start at Level 1 and expand as your project grows.
π Level 1"I just want better shipping"Drop in /git commit and /git pr.No governance overhead β just better, safer shipping. |
ποΈ Level 2"I want project structure"Use /team-start, /phase-status, /bug-report.Phase-based development without full team simulation. |
ποΈ Level 3"I want full governance"Enable all hooks, activate agent teams, full session logging. Enterprise-grade traceability out of the box. |
π» VSCode Extension (UniOpsQC Hub)
UniOpsQC Hub is a companion VSCode extension that gives you a visual dashboard alongside Claude Code.
Install: Search for UniOpsQC Hub or RoundTable Hub in the VSCode Marketplace, or install extension ID unicorntech.roundhub.
What It Does
The extension does not run Claude Code β it is a command launcher and log viewer that works alongside the CLI.
| Button | What It Does |
|---|---|
| Quick Actions | Copies a /command to your clipboard β paste it into Claude Code to run |
| SESSION LOGS | Displays your RoundTable session log files for the active project |
| FRAMEWORK STATUS | Shows the installed framework version (requires a .git repository) |
| Push to Hub | Syncs your RoundTable logs to a cloud dashboard (subscription feature β not yet available) |
| Update Preview | Copies the /template preview command to your clipboard β paste into Claude Code to run |
| Refresh | Reloads the extension panel to reflect the latest file changes |
Two Versions β What Each Shows
The extension panel displays two version numbers:
| Version | What It Is | Where It Comes From |
|---|---|---|
Framework version (e.g., v2.0.0) |
The UniOpsQC template version | Read from your project's .git tags or template-version.json |
Extension version (e.g., v1.6.0) |
The VSCode extension itself | The extension's own release version in the Marketplace |
[!TIP] The framework and extension are versioned independently. A newer extension does not mean a newer framework, and vice versa.
Centralized vs. Decentralized Projects
When you add a project in the extension, you will be asked for a Project Name and Project Root. UniOpsQC supports two project modes (set in .claude/ProjectEnvironment.md):
| Mode | When to Use | Root Path Points To |
|---|---|---|
| Centralized | Greenfield or solo projects | The folder containing both .claude/ and your source code |
| Decentralized | Pre-existing codebases | The planning hub folder (containing .claude/), which is separate from the source code |
π₯ Teams
graph TD
Commander["π Commander<br/>(You)"]
AM["π― Overseer<br/>AM Β· MT Β· AS"]
MON["ποΈ Monolith<br/>Backend Β· DB Β· Cloud"]
SYN["β‘ Syndicate<br/>API Β· Security"]
ARC["π¨ Arcade<br/>Frontend Β· UI"]
CI["π¬ Cipher<br/>Forensics Β· Recovery"]
Commander --> AM
Commander --> CI
AM --> MON
AM --> SYN
AM --> ARC
style Commander fill:#f0a500,color:#000,stroke:#f0a500
style AM fill:#1e6fb5,color:#fff,stroke:#1e6fb5
style MON fill:#1a7a4a,color:#fff,stroke:#1a7a4a
style SYN fill:#b52020,color:#fff,stroke:#b52020
style ARC fill:#7c3aed,color:#fff,stroke:#7c3aed
style CI fill:#444,color:#fff,stroke:#666
| Team | Domain | Style |
|---|---|---|
| Overseer | Project management, architecture decisions | Balanced, cautious, standards-compliant |
| Monolith | Core backend, infrastructure, DB schema, cloud, docs | Verbose, type-safe, bulletproof |
| Syndicate | API integration, query optimization, security | Pragmatic, terse, performance-focused |
| Arcade | Frontend UI, gamification, creative systems | Clever, modern, innovative |
| Cipher | Hardware diagnostics, disk forensics, RAID recovery | Surgical, zero-write, verify-before-acting |
β‘ Skills
| Category | Command | Purpose |
|---|---|---|
| π Workflow | /team-start [Team] [Project] [Phase] [free\|hold] |
Formal team kickoff |
| π Workflow | /phase-status [Project] |
Full project phase + ticket status |
| π Workflow | /compact-resume |
Post-compact re-orientation |
| π Workflow | /overseer-report [ID] |
File OverseerReport entry |
| π Planning | /bug-report [Project] [desc] |
Create bug fix ticket + folders |
| π Planning | /mod-log [Project] [name] |
Create modification ticket + folders |
| π Planning | /sub-feature [Project] [name] |
Create sub-feature ticket + folders |
| β Quality | /audit [Project] [scope?] |
End-to-end multi-domain audit β finds gap bugs |
| β Quality | /git status |
Quick git state overview β branch, divergence, working tree |
| β Quality | /git commit [branch?] |
Governed commit β safety gates, 2-pass review, ticket gate |
| β Quality | /git pr [branch?] |
Governed PR β safety gates, review, test, push, pull request |
| β Quality | /git sync [remote?] [branch?] |
Governed sync β fetch upstream/origin, compare, merge/rebase |
| β Quality | /git lookback [period?] |
Retrospective β rebase-aware git + session data + decision audit |
| π Persona | /Overseer /Monolith /Syndicate /Arcade /Cipher |
Switch active team persona |
| π§ Framework | /template [action] |
Version check, diff, update, rollback |
Persona Skills
| Command | Purpose |
|---|---|
/Overseer /Monolith /Syndicate /Arcade /Cipher |
Switch active team persona |
Framework Management
| Command | Purpose |
|---|---|
/template version |
Quick check β your installed version + component count |
/template check update |
Compare local vs latest remote version, warn if outdated |
/template preview |
Upgrade impact analysis β benefits, risks, and recommendation |
/template changelog [version?] |
View changelog, optionally filtered by version |
/template apply |
Upgrade with auto-backup + AI Smart Merge for conflicts |
/template rollback [version?] |
Restore any previous version from versioned backups |
π Rules (Path-Scoped)
Policy rules in .claude/rules/ load automatically based on file context:
| Rule | When It Loads | Key Rules |
|---|---|---|
governance.md |
Always | Plan-before-code, no-code-before-ticket, ticket/briefing standards, phase gates |
logging.md |
Always | Session logging, rotation, handover, OverseerReport, TeamChat |
debugging.md |
Code files (.ts, .js, .py, etc.) |
Instrument-first, probe standards, cross-layer trace, gap bugs |
testing.md |
Test files (*.test.*, *.spec.*) |
Unit tests, regression gates, living docs |
codebase-scanning.md |
Always | L1/L2/L3 tiered scan protocol, completeness checks |
parallel-execution.md |
Always | ZCB guarantee, ticket ownership, multi-session |
skills-and-subagents.md |
Always | Skill format, orchestration modes, subagent triggers |
πͺ Hooks (Automated Enforcement)
Hooks are defined in .claude/settings.json under the "hooks" key. Scripts live in hooks/scripts/.
| Hook | Event | What It Does |
|---|---|---|
SessionStart |
Session start | Confirms RoundTable governance framework is active |
check-ticket-exists |
PreToolUse (Edit/Write) | Warns if no ticket exists before code edits |
log-file-change |
PostToolUse (Edit/Write) | Logs file changes to session audit trail |
| Protected files | PreToolUse (Edit/Write) | Prompt hook β blocks edits to CLAUDE.md, policies, agents without authorization |
[!WARNING] Windows note: Hook scripts require Git Bash or WSL. Ensure
bashandjqare available in your PATH. Scripts use#!/usr/bin/env bashshebangs and Unix path separators.
π Playwright MCP (Browser Automation)
Verification Scholars can use Playwright for UX Smoke Test Gates and User Journey Walkthroughs.
Configuration: .mcp.json at project root.
π Project Structure
your-project/
βββ .claude/
β βββ CLAUDE.md # Core policy (entry point)
β βββ ProjectEnvironment.md # Project registry
β βββ settings.json # Permissions + hooks + protected file rules
β βββ agents/ # 5 team agent definitions
β βββ rules/ # 7 path-scoped rule files
β βββ skills/ # 21 slash command skills
β β βββ git/ # Unified VCS: status, commit, pr, sync, lookback
β β β βββ checklists/ # Critical, informational, suppressions
β β βββ audit/ # Multi-domain gap bug finder
β β βββ ...
β βββ policies/ # 9 detailed policy files (Β§1βΒ§9)
β βββ team_chat/ # Team communication logs + Cipher diagnostics
βββ hooks/ # Hook scripts (config in .claude/settings.json)
β βββ scripts/ # check-git-workflow.sh, check-ticket-exists.sh, log-file-change.sh
βββ .mcp.json # Playwright browser automation
βββ plugin.json # Plugin manifest
βββ RoundTable/ # Session logs (created at runtime)
π Policy Reference
π View all 9 policies (Β§1βΒ§9)
| Policy | What It Covers |
|---|---|
| Β§1 Logging & RoundTable | Session logging, log format, rotation policy |
| Β§2 Tickets & Briefings | Phase dispatch, briefing mail, ticket standards, UX smoke test |
| Β§3 Team Chat & Handover | Cross-team protocol, OverseerReport, handoff files |
| Β§4 Development Structure | Project organization, planning-first workflow, error catalog |
| Β§5 Pre-Existing Codebase | Tiered scan protocol (L1/L2/L3), completeness verification |
| Β§6 Debugging Protocol | Instrument-first rule, probe standards, gap bug detection |
| Β§7 Parallel Execution | ZCB guarantee, ticket ownership, dependency signals |
| Β§8 Skills & Subagents | Skill catalogue, orchestration modes, subagent standards |
| Β§9 Multi-Session | One-session-per-project, project-prefixed logging |
π§ Customization
π§ How to customize UniOps Quantum Cycle for your project
UniOps Quantum Cycle is designed to be forked and customized:
- Rename team members β edit agent files to match your preferred code names
- Add/remove teams β create new agent files or remove unused ones
- Adjust policies β modify policy files in
policies/ - Add skills β create new
.claude/skills/[name]/SKILL.mdfiles - Tune rules β edit
.claude/rules/files to adjust enforcement level - Change authority naming β replace "Commander" with your preferred title
- Toggle hooks β switch from warning to blocking mode in hook scripts
π¦ Requirements
- Claude Code CLI installed
- Claude API access (Anthropic API key)
π€ Author
Unicorn Tech Integration Co., Ltd.
- Website: unicorntechint.com
- GitHub: @VarakornUnicornTech
- Discord: Join our community
- Location: Bangkok, Thailand
βοΈ License
MIT License β see LICENSE for details.
UniOps Quantum Cycle v2.0.0
Built with β€οΈ by Unicorn Tech Integration Co., Ltd.
Β· Bangkok, Thailand πΉπ
Getting Started Β· Contributing Β· Changelog Β· Discord Β· License