@withkynam/vibecode-pro-max-kitPublic

Harnesses#Claude Code #Codex #Cursor #Windsurf#Coding #Testing #Product

Plan-first harness for Claude Code and Codex

This repository installs a full agent workflow into an existing project, rather than a finished app. It combines phase-gated process files, reusable skills, specialist agents, and lifecycle hooks so your coding agent can research, plan, execute, and update context in order. The install script detects whether you are starting fresh or upgrading and tells you the next command to run.

1,120 stars•233 forks•JavaScript•Updated 2mo ago

Who it's for

Builders who want their coding agent to keep context, follow a plan, and resume work across sessions.

What it delivers

You can run larger agent-led projects with less context loss, less rework, and more consistent execution.

What it does

RIPER-5 workflow

A 7-phase flow: Research, Spec, Innovate, Plan, Validate, Execute, and Update Process.

Self-healing loops

PVL and EVL loops re-check plans and tests, then fix gaps before moving on.

Autopilot modes

Quick, fast, and full lanes let you start hands-free runs at different levels of ceremony.

Persistent project memory

Progress notes are written to disk so a run can resume after a reset without losing place.

Specialist agents and skills

The kit ships with 15 agents and 33 skills that are auto-discovered and routed by the workflow.

Lifecycle hooks

Hooks add safety rails and automatic context loading around agent actions.

Non-destructive install

The installer backs up existing config and avoids overwriting your project files.

Cross-tool support

It mirrors setup for Claude Code and Codex, and is presented as usable across many agents and editors.

How to get it

1There is only one command, and it works for everyone. Run it inside your project folder.…

curl -fsSL https://raw.githubusercontent.com/withkynam/vibecode-pro-max-kit/main/install.sh | bash

2Your main session is a coordinator (called the orchestrator), not a worker. It does four…

Your request
  → Step 0: Skill Discovery (scan 33 skills, match keywords, attach candidates)
  → Detect intent (feature / bug / question / refactor / UI) + score ambiguity
  → Route to the right agent in a fresh context window
  → Monitor: step compliance, status codes, loop driving

3Run

# 🐛 Bug fix
You: "login redirect is broken"
→ Routes to vc-debugger → gathers evidence FIRST → 2-3 competing hypotheses
→ Systematically eliminates each → root cause with proof chain
→ execute-agent implements the fix → EVL re-test → quality pipeline

4Run

# ⏩ Fast mode
You: "ENTER FAST MODE - add rate limiting middleware"
→ Compressed RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE in one pass
→ Mandatory safety pause after VALIDATE → you review → "ENTER EXECUTE MODE"

5Run

# 🤖 Autopilot (hands-free)
You: "autopilot full: build a notifications system"
→ ONE consolidated clarification round → provisional /goal block (standing consent)
→ Drives the full RIPER-5 sequence autonomously, pausing only on hard stops

6Run

# 🏗️ Large program
You: "build a full testing platform"
→ Umbrella plan + phase plans in a feature folder
→ Each phase inner loop: research → innovate → plan → PVL → execute → EVL → update
→ Progress survives context compaction — durable reports on disk

README

Built by world-class engineers, for vibecoders at
flowser.ai — AI Agents with computers for GTM

vibecode-pro-max-kit

Flow like water

"Total Concentration — Spec Breathing, Tenth Form: the Vibe Flow never breaks."
— Tanjiro Kamado

Drop this into any project. Your AI agent gets a complete plan-first dev process — 7 gated phases, self-healing check loops, and autopilot that runs start to finish without losing its place.

📦 One-command install One `curl` line drops it into any project. It detects new vs. returning users and never overwrites your files.	🌐 Works everywhere Any tech stack, any language, and any AI coding agent — Claude Code, Codex, Cursor, Windsurf, Copilot, and more.
🧭 RIPER-5 plan-first workflow 7 gated phases (Research → Spec → Innovate → Plan → Validate → Execute → Update-Process) stop the agent from jumping straight to code.	🚀 Autopilot mode (quick / fast / full) Start a hands-free run at any phase with a single phrase. Three lanes match the ceremony to the risk.
🎯 `/goal` — the run-until-done token One copy-pasteable block keeps the agent running phase after phase without stopping — and resumes the run in a fresh session.	🔁 PVL + EVL self-healing loops Plan-check-fix and test-check-fix loops find gaps, fix them, and re-check on their own — up to 10 cycles each.
🔍 vc-autoresearch A reusable find-gaps → fix → repeat loop you can point at plans, tests, specs, docs, or evals.	🧪 Feasibility probes Test-before-you-build verdicts (VIABLE / NOT-VIABLE) before the agent commits to any design approach.
🎛️ Smart strategy picker Before each phase it weighs one agent vs. many vs. a coordinated team — with cost estimates — and picks the cheapest that fits.	🧮 Smart model use The expensive model only writes code; the cheaper model does everything else. Lower cost, same quality.
🤔 Intent clarification When a request is vague, the agent asks a few sharp questions up front instead of guessing and building the wrong thing.	🛡️ 36 validators Mechanical correctness checks — not opinions — guard the kit's own structure and catch drift before it ships.
🏗️ Phase programs Large projects are split into independent phases with quality gates between them, so big work doesn't fall apart.	🔀 Programs that reshape themselves As it learns, the agent inserts new phases, reorders work, and skips blocked steps — the plan adapts on the fly.
🧠 Never loses its place Progress notes are written to disk every phase, so a run survives a memory reset and picks up exactly where it left off.	📚 Self-improving project memory It learns your codebase on setup and keeps its own shared notes current after every feature ships, so docs never go stale.
⚡ Quick Fix + Fast Mode Light lanes for small changes skip the heavy ceremony, so a one-line fix stays a one-line fix.	🧱 Layered, auto-discovered skills Skills are organized in clear layers and discovered automatically — the agent always finds the right tool for the step.
🤖 15 agents · 33 skills · 10 hooks A full team of specialized agents, reusable skills, and safety hooks, all wired together out of the box.	🔄 Full kit lifecycle Install, setup, update, and publish are all one command each — keeping every project on the latest kit safely.
📝 SPEC — your plain-language sign-off Before any design, you state what to build in simple user stories — the cheapest place to catch a misunderstanding.	🎯 Always checks your intent Every later phase measures back against your SPEC: is what we're building actually what you asked for?

The simplest, most flexible, team-friendly coding kit for

Works across any tech stack, any language, any project

Tech Stack Row 1
Tech Stack Row 2
Tech Stack Row 3

Not just for show. When you run vc-setup, agents scan your codebase,
detect your stack, and build project-specific knowledge groups that every skill reads before it works.
Other harnesses lock agents to one language — rust-review-agent, python-linter — useless elsewhere.
This one adapts to any combination above and builds up knowledge as you ship.

⚡ Get Started — One Command, 30 Seconds

Prerequisites: Node.js ≥ 22, git, bash (macOS / Linux / WSL / Git Bash; on Alpine: apk add bash).

Windows: the installer is a bash script — run it inside Git Bash (ships with Git for Windows) or WSL, not PowerShell or cmd.exe. Both work out of the box: the installer detects Windows shells and, when symlinks aren't permitted, automatically falls back to copying (install still completes). For true symlinks (so Codex auto-reflects vc-update changes), enable Developer Mode.

There is only one command, and it works for everyone. Run it inside your project folder. It detects whether you are a new or returning user, installs safely without overwriting your files, and then tells you the exact next thing to say.

curl -fsSL https://raw.githubusercontent.com/withkynam/vibecode-pro-max-kit/main/install.sh | bash

When it finishes, it prints one of two messages — read the bottom of the output and do exactly what it says:

🆕 Fresh project

Installer detects no harness and prints:

Next: Run: claude → Say: "Run vc-setup"

→ Open your agent and say Run vc-setup

_{vc-setup detects your tech stack, creates the process/ folder, scans your codebase, and fills in your real architecture, conventions, and test commands — a conversation, not a checklist.}

🔄 Existing harness (upgrade)

Installer detects a prior install and prints:

Next (upgrade detected): Run: claude → Say: "Run vc-update"

→ Open your agent and say Run vc-update

_{vc-update pulls the latest version and, if it finds old-format plans or folders, gives you a ready-to-paste prompt to finish the move with zero data loss. Your process/ is never touched.}

💡 You never have to guess the command. install.sh routes you: fresh → vc-setup, upgrade → vc-update. Re-running install is always safe — it never breaks things. Codex users: run /vc-setup (or /vc-update) instead of saying it in chat.

📦 What install puts on disk (non-destructive)

your-project/
├── .claude/
│   ├── agents/              # 🤖 15 agent definitions (.md)
│   ├── skills/              # ⚡ 33 skills (each a dir with SKILL.md)
│   └── hooks/               # 🪝 10 lifecycle hooks (.cjs / .mjs)
├── .codex/agents/           # 🔄 Mirrored agents for Codex
├── .agents/skills →         # 🔗 Symlink to .claude/skills (Codex discovery)
├── CLAUDE.md                # 📋 Orchestrator + routing rules
├── AGENTS.md                # 📖 Agent + skill registry (cross-tool)
└── process/
    └── development-protocols/  # 📜 22 shared workflow docs (seeded by install)
                                #    context/, plans, features → built by vc-setup

Non-destructive. Your existing .claude/skills/, .claude/agents/, process/, and settings.json are never wiped. Only kit-owned files are written or updated.
Existing config? Backed up to .vibecode-backup/; your settings.json is restored afterward.
Existing CLAUDE.md? Backed up as CLAUDE.md.pre-vibecode.
Existing process/? Never touched by install — vc-setup / vc-update migrate it interactively, showing you the diff first.

One-time first-install caveat: if you have custom skills/agents whose names start with vc- (the reserved kit namespace) and have never run install before, the stale-removal step may flag them. After install, run ls .claude/skills/ .claude/agents/ to confirm. Use a non-vc- prefix (my-, team-, proj-) for your own additions to avoid this entirely.

🤖 Prefer to drive setup from your agent? (full prompt)

Open Claude Code or Codex with your project folder as the working directory, then paste:

First, install the vibecode-pro-max-kit agent harness by running this command:

curl -fsSL https://raw.githubusercontent.com/withkynam/vibecode-pro-max-kit/main/install.sh | bash

After install completes, run vc-setup and follow the full interactive flow:

1. DETECT — Read package.json (or go.mod, Cargo.toml, pyproject.toml, etc.), detect my
   stack: framework, package manager, monorepo structure, test framework, database, auth.
   Also check for any existing .claude/, process/, or context files.
2. SHOW ME WHAT YOU FOUND — Summarize detection and wait for me to confirm. If this is an
   existing project, tell me what looks good vs what could be improved.
3. ASK ME ABOUT THE PROJECT — Have a real conversation. Ask follow-ups, probe anything
   vague, keep going until you genuinely understand it. Summarize back and confirm.
4. SCAFFOLD — Create the process/ directory. If process/ already exists, show me the plan
   and wait for approval. Never silently move or delete my files.
5. STUDY — Deep-scan and populate process/context/all-context.md with REAL content: repo
   structure, stack + versions, patterns, import aliases, env vars, routes, schema, tests.
   No placeholder text.
6. VALIDATE — Run all validation checks to confirm everything is wired correctly.

Rules: read and preserve good existing context; show me a summary before each major change
and wait for my OK; never create empty placeholder files; ask before reorganizing.

Table of Contents

At a Glance · The Problem · The Fix
Vibe Coding Revolution · Who Is This For · How This Compares · What Makes This Different
How It Works: The Coordinator · The RIPER-5 Lifecycle · Intent Clarification
The Two Quality Loops (PVL + EVL) · Strategy Compare + Model Policy · Autopilot Mode · Feasibility Probes + Validators
Built-in Safety Systems · Pre-Implementation Intelligence · Quality Pipeline
Plan Lifecycle · Phase Programs · Context Groups · Feature Folders · Skill Layers · Self-Improving Memory
What's Inside · Quick Fix + Fast Mode · Kit Lifecycle · Contributing

🎁 At a Glance

🤖

15

Agents
_{One per phase + 6 specialist agents}

⚡

33

Skills
_{20 workflow + 13 helper, matched by keyword}

🪝

10

Hooks
_{Safety rails + automatic context loading}

📜

22

Protocols
_{Shared rules every agent follows}

🛡️

36

Validators
_{Automated checks that catch errors before they ship}

🔧

7

Tools
_{Claude Code · Codex · Cursor · Windsurf · Antigravity · OpenCode · Copilot}

🌍

10

Languages
_{EN · 中文 · 日本語 · 한국어 · VI · PT · DE · FR · ES · हिन्दी}

⚡

30s

Install
_{One command, then your agent guides the rest}

🛩️

Autopilot
_{3 lanes (quick / fast / full) — start at any phase, runs start to finish without stopping}

📌

/goal blocks
_{Short copy-pasteable texts that resume hands-free runs across sessions after a reset}

🔁

vc-autoresearch
_{Find-gaps → fix → repeat loop (shared tool for plans, tests, and evals)}

🔬

Feasibility probes
_{Test-before-you-build verdicts (VIABLE / NOT-VIABLE) before locking in a design}

🔥 The Problem

You ask Claude to "add webhook support." It immediately starts writing code. No questions about your architecture. No check on existing patterns. No plan. You get 400 lines that don't fit your codebase, and you spend an hour fixing it.

But that's just the surface. The deeper problems hit harder:

🧠 Context dies every session Your agent forgets everything it learned. Same mistakes, same questions, every time. No memory, no compounding knowledge.	📄 Docs go stale instantly You wrote great context docs last week. They're already outdated. Nothing auto-updates them as the codebase evolves.
💥 Big tasks collapse mid-way The context window fills, state is lost, the agent starts hallucinating. You restart from scratch on hour 3.	🤝 No specs, no review, no collaboration Your PM can't review what the agent is about to build. There is no written plan to share, discuss, or approve before code is written.
🎭 Architecture decisions are hallucinated The agent invents patterns instead of researching how other codebases solved the same problem.	🚀 Nothing verifies "done" The agent says "all tests pass" — but it never independently re-ran them. You find out in production.

Your agent has intelligence but no process, no memory, and no way to collaborate with your team. Whether you're a developer, a PM, or a CEO who just started vibe coding — this hits everyone the same way, and the fix is the same: give your agent a real development process.

🛠️ The Fix

This kit installs a complete development system into your project — not just a CLAUDE.md, but 15 specialized agents, 33 skills, 10 hooks, and 22 protocols — with a step-locked workflow that makes your agent understand before it builds, and prove before it ships.

📋 Plan-first approach _{PMs and devs review the same written plan before any code is written}	🔄 Self-improving knowledge _{Updates itself every time a feature ships — docs never go stale}
⚡ Hands-free execution _{Survives session resets — runs for hours, not minutes}	🧬 Architecture research _{Studies real codebases before making design decisions}
✅ Two quality checks _{Plans are checked before coding; tests are re-run independently after}	🧭 Smart knowledge routing _{Loads only what is relevant — not your whole knowledge base every time}

The full RIPER-5 flow — 7 phases, every step gated

%%{init: {'theme': 'base', 'themeVariables': {'fontSize': '14px', 'lineColor': '#8888AA'}} }%%
flowchart TD
    R["RESEARCH\nread-only facts"]
    S["SPEC\nrequirements doc"]
    I["INNOVATE\n2-3 approaches"]
    P["PLAN\ndetailed checklist"]
    V["VALIDATE\nplan → contract\n(PVL loop)"]
    E["EXECUTE\nimplement\n(EVL loop)"]
    U["UPDATE PROCESS\ncapture + archive"]

    R -->|"go"| S
    S -->|"go"| I
    I -->|"go"| P
    P -->|"ENTER VALIDATE"| V
    V -->|"Gate: PASS"| E
    E -->|"gates green"| U

    style R fill:#1565C0,stroke:#0D47A1,color:#FFFFFF
    style S fill:#0277BD,stroke:#01

Files in the repo

Repository payload•23 top-level entries

.agents— Agent plugin files
.claude— Claude Code skills, agents, commands, hooks
.codex— 4 items
.github— GitHub workflows and templates
assets— 1 item
docs— Documentation
process— 5 items
.gitattributes
.gitignore
.markdownlint.json
AGENTS.md— Instructions for Codex and other agents
CHANGELOG.md
CLAUDE.md— Main orchestration and routing rules.
compute-sync-plan.mjs
CONTRIBUTING.md
e2e-kit-flows.test.mjs
install.sh— Install script
LICENSE— License
MIGRATION.md
README.md— The README
resolve-manifest.mjs
SECURITY.md
vc-manifest.json

Discussion (0)

Ask about usage, or say what you built with it

No comments yet. Be the first to say what this is good for.

More harnesses

affaan-m/

ECC

affaan-m/ECCHarnesses

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

258k

shanraisshan/claude-code-best-practiceHarnesses

from vibe coding to agentic engineering - practice makes claude perfect

66k

ruvnet/rufloHarnesses

🌊 The original agent meta-harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, RAG integration, and native Claude Code / Codex / Hermes and many more Integrated

72k

cobusgreyling/loop-engineeringHarnesses

Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit, loop-init, loop-cost.

11k

open-gsd/

gsd-core

open-gsd/gsd-coreHarnesses

Git. Ship. Done - Core

9.3k

1jehuang/jcodeHarnesses

The most RAM efficient harness

19k