By bishnubista
PLAN.md execution plugin for Claude Code that runs every task through an implementation subagent, objective quality gate, and independent reviewer before completion. It auto-detects stack commands across Node, Python, Kotlin, Go, Rust, and Swift, supports custom command overrides, and manages phase workflows for branch setup, checkpointed orchestration, troubleshooting investigations, and pre-PR validation.
Implements a specific task from a development plan. Asks clarifying questions first, then implements, writes tests, validates, and commits with a structured report.
Independent code reviewer that verifies implementation against spec with explicit distrust of the implementer's report. Checks both spec compliance and code quality in one pass.
Stack-aware pre-PR validation gate. Auto-detects stack, validates typecheck + lint + build + tests. Use when the user says 'run gate', 'validate', 'check before PR', or 'run checks'.
Create a structured investigation document for complex bugs. Use when a bug requires more than a quick fix — tracks hypotheses, trials, root cause, and lessons learned.
Stack-aware orchestrator for PLAN.md execution. Sequential pipeline: implementer agent > build gate > reviewer agent. Fresh context per stage prevents bias.
Phase lifecycle management. Use 'start N [description]' to begin a phase (branch + PLAN.md update) or 'finish [N]' to complete it (gate + PR creation).
Show current phase, task progress, and orchestration state. Use when the user says 'status', 'progress', 'where are we', or 'what's left'.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
PLAN.md-driven development with quality gates for Claude Code.
Each task flows through: implement (subagent) > build gate (pass/fail) > review (independent subagent). Fresh context per stage prevents the failure mode where AI agents mark their own homework.
/plugin marketplace add bishnubista/plangate
/plugin install plangate@plangate
Or run /plugin and install from the Discover tab.
claude --version)gh) authenticated if you use /plangate:phase finish to create PRs.plangate.json)Use MARKETPLACE_SUBMISSION.md as a copy-paste pack for Claude Plugin Directory submission fields.
Included assets:
MARKETPLACE_SUBMISSION.mdassets/plangate-marketplace-card.svgAll commands are provided by plugin skills (no legacy commands/*.md wrappers).
| Command | What it does |
|---|---|
/plangate:orchestrate [N] | Execute phase N tasks through the full pipeline |
/plangate:gate | Typecheck + lint + build + tests validation |
/plangate:status | Show current phase, task progress, orchestration state |
/plangate:phase start N / finish | Branch creation, PLAN.md updates, PR creation |
/plangate:investigate {name} | Structured investigation doc for complex bugs |
For each task in a phase, the orchestrator runs:
1. IMPLEMENTER (Sonnet subagent)
Implement > write tests > self-validate > commit
2. BUILD GATE (Bash, no AI)
typecheck > lint > build — objective pass/fail
3. REVIEWER (Sonnet subagent, independent)
Spec compliance + code quality + distrust of implementer
4. UPDATE PLAN.MD
Check off completed task
If any stage fails, a fix subagent is dispatched and the gate re-runs. Max 2 retries per stage.
The reviewer receives the original task spec and the git diff — never the implementer's self-assessment. It's explicitly told: "Do NOT trust the implementer." This catches skipped features, fake tests, missed edge cases, and bugs from blindly following patterns.
/plangate:gate runs validation and reports results:
| Check | Status | Details |
|------------|--------|----------------------|
| Typecheck | PASS | clean |
| Lint | PASS | clean |
| Build | PASS | clean |
| Tests | PASS | 24 passing, 0 failing|
Verdict: GATE PASSED
The gate stops on first failure — build won't run if typecheck fails. Non-negotiable before every PR.
/plangate:phase start 2 core-api # Create branch feat/phase-2-core-api
/plangate:orchestrate 2 # Run all Phase 2 tasks through pipeline
/plangate:phase finish # Gate + push + create PR
For bugs that need more than a quick fix:
/plangate:investigate auth-token-expiry
# Creates docs/investigations/2026-02-07-auth-token-expiry.md
Tracks hypotheses, trials, root cause, and lessons learned. Follows the 3-fix rule: if 3 fixes fail, stop and question the architecture.
The session hook auto-detects your project stack. No manual configuration needed.
| Marker | Stack | Package Manager |
|---|---|---|
bun.lock | node/nextjs | bun |
pnpm-lock.yaml | node/nextjs | pnpm |
yarn.lock | node/nextjs | yarn |
package-lock.json or package.json (fallback) | node/nextjs | npm |
pyproject.toml | python | uv |
build.gradle.kts | kotlin | gradle |
go.mod | go | go |
Cargo.toml | rust | cargo |
Package.swift | swift | spm |
Override with .plangate.json:
{
"commands": {
"typecheck": "your-custom-typecheck",
"lint": "your-custom-lint",
"build": "your-custom-build",
"test": "your-custom-test"
}
}
There is no /install-plugin command. Use /plugin install plangate@plangate after adding the marketplace.
The skill reads PLAN.md for tasks. Create one with - [ ] checkboxes.
The hook needs lockfiles or package.json. Run bun init, npm init, etc., or create .plangate.json with custom commands.
npx claudepluginhub bishnubista/plangate --plugin plangateAutomatically fix CodeRabbit PR review comments — gathers issues, fixes in batches with build validation, resolves GitHub threads
SAFE-T-first security scanning adapters for LLM-powered applications, with OWASP LLM/Agentic and agentic controls as secondary mappings.
Script-backed operations plugin for Bun projects with adapter profiles (Next.js or TanStack, Railway or Fly.io). It enforces deterministic init, migration, deploy, and incident workflows with production confirmation gates, artifacts, and rollback verification.
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Plan iron, verify real. Ironclad planning with independent verification chain. Turns any input into a bulletproof plan, executes with TDD, verifies with independent agents.
HarnessFlow — a harness that drives AI coding agents from a raw idea to a working app: product-layer shaping (hf-shape/hf-skeleton), main-chain discipline (SDD + TDD) along frame -> plan -> build -> verify -> ship, exploration mode for disposable prototypes, mechanical gates (hf_gate.py init/status/next/run/check), demo-gated acceptance, and pluggable ext-* domain extensions.
Harness engineering for Claude Code — hook-enforced dual review, state-machine gates, and fail-closed safety where it counts.
Software engineering workflows with skills for planning, implementation, quality review, and structured thinking, plus a suite of specialist agents
Language-agnostic development process harness implementing the Stateless Agent Methodology (SAM) 7-stage pipeline with ARL human touchpoint model and Voltron-style language plugin composition. Provides orchestration, workflows, planning, verification, and testing methodology that any language plugin can compose with.