claude_harness_eng_v6

Plugin claude_harness_eng_v6 from marketplace claude-harness-local in cwijayasundara/claude_harness_eng_v6. Commands read from the repo's manifest — 13 days ago.

Skills (54)

• advise

  Invoke the frontier advisor for a structural re-rank / unblock / design pivot. Compact brief only.

• agent-readiness

  Show how mature/safe this codebase is for heavy AI-agent use — a synthesis dashboard across 8 pillars, aggregating signals the harness already collects. Read-only report; aggregates state already on disk.

• attestation

  Generate a per-commit, durable compliance attestation (with a sha256 corruption-detecting integrity checksum) from the harness control inventory, the branch-protection/deploy-gate verify outputs, the gate verdict, and the ratchet baselines — then commit the record. Use at /gate or in CI to produce c

• author-prompt-surface

  Use when creating or editing .claude/agents/*.md, .claude/skills/*/SKILL.md, or .claude/commands/* — apply docs/prompting-standards.md (trigger conditions, model-agnostic bodies, no reasoning-as-text, effort floors).

• auto

  Autonomous build loop with Karpathy ratcheting, GAN evaluator, and session chaining. Iterates story groups until all features pass or stopping criteria met.

• brd-extract

  [Internal pipeline stage — dispatched only as a fallback when prd-extract.js cannot parse a source document. Prefer `node .claude/scripts/prd-extract.js`.] Extract the source document's requirement spine into frd-requirements.json, adopt it deterministically, and return counts only.

• brd-render

  [Internal pipeline stage — dispatched by /brd once the interview and clarifications are recorded; invoke directly only to re-render an approved intake.] Expand the confirmed requirement spine and clarification log into the BRD analysis pack, the BRD document, and the deterministic grounding and taxo

• brd

  [Internal pipeline stage — run by /build; invoke directly only as a power user.] /brd --prd is adopt-only (scripts, no interview) unless --full.

• brownfield

  Discover and map an existing codebase before planning or changing it. Add --seams "<goal>" to also rank the safest cut-points for that goal.

• change

  Change the behavior of existing code — story-driven by default, or --issue N for a GitHub bug fix. Test-first, full verification, code review.

• checking-coverage-before-change

  Use when about to edit any existing (non-greenfield) symbol — before the first Edit/Write to production code in /refactor, /change, or /vibe — to learn which tests cover it and route uncovered code to pinning or sprouting. [Internal discipline — applied automatically by pipeline agents mid-task; dir

• checking-migration-safety

  Use when a change touches persisted data shape — expand-contract and prove the down-migration. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]

• clarify

  [Internal pipeline stage — run by the planning stages; invoke directly only as a power user.] Bounded clarification gate for resolving product, domain, API, security, or architecture uncertainty without exhausting the user.

• code-gen

  Code generation quality principles — TDD, typing, error handling, logging, API integration, LLM integration.

• code-map

  [Internal pipeline stage — run by first-source /auto, /brownfield, and /seam-finder; invoke directly only as a power user.] Build the deterministic code graph.

• context

  Build a bounded, cited context pack from the living DeepWiki/code-map before broad source reads. Use in brownfield lanes and whenever source orientation could otherwise require large file reads.

• deepagents-code

  Build long-running, production-ready agents with DeepAgents — the opinionated harness on top of LangGraph/LangChain providing filesystem access, task planning, subagent delegation, and context management out of the box. Use for long-running coding/research/multi-step tasks where you'd otherwise hand

• deploy

  [Internal pipeline stage — run by /build; invoke directly only as a power user.] Generate Docker Compose stack, Dockerfiles, environment config, and init.sh bootstrap script.

• design-render

  [Internal pipeline stage — dispatched by /design after its decisions gate passes; invoke directly only to re-render an approved decisions file.] Expand design-decisions.json into architecture, program-design.md, contracts, component-map, and UI mockups only when UI stories exist.

• design

  [Internal pipeline stage — run by /build (use --doc-only standalone for an ARB narrative); invoke directly only as a power user.] Generate system architecture, program-design.md, machine-readable schemas, and UI mockups only for UI stories.

• evaluate

  [Internal pipeline stage — run by /auto and /gate; invoke directly only as a power user.] Run the application and verify sprint contract criteria via API tests, Playwright interaction, and schema validation.

• fastapi-code

  Use when writing a FastAPI route, Depends(), Pydantic model, or TestClient test. Not for SQLAlchemy or non-FastAPI frameworks.

• feature

  Brownfield change route — take an existing-code feature request from intent to a reviewed PR, scaling from a single /change to an epic via /spec→/design→/auto. Linear-tracked, backed by a committed DeepWiki.

• fix-from-diagnostics

  [Internal pipeline stage — run by /auto self-heal and /implement validation when lint/type error volume is high; invoke directly only as a power user.] Turn compiler/linter output into a sharded work queue; fix per package with optional adversarial review — no full monorepo suite mid-shard.

• gate

  Run the adaptive pre-merge quality gate: deterministic checks, evaluator, diff review, and security review only when the diff crosses a security/data/API boundary. (Renamed from /review to avoid colliding with Claude Code's native /review PR-review command.)

• implement

  [Internal pipeline stage — run by /auto (follow with /gate); invoke directly only as a power user.] Generate production code and tests for a story group using agent teams for parallel execution.

• install-framework-packs

  [Internal pipeline stage — run by /scaffold; invoke directly only as a power user.] Verify agent-framework skill packs declared in project-manifest.json#framework_skill_packs and print normal-terminal install commands for missing packs. Use after /scaffold reports PENDING MANUAL INSTALL, after manua

• keeping-refactors-pure

  Use when committing any change that includes structural work (rename, move, extract, reorder) in an existing codebase — keeps refactor commits behavior-free and behavior commits refactor-free so regressions stay attributable. [Internal discipline — applied automatically by pipeline agents mid-task;

• langchain-code

  Build LangChain agents in Python — create_agent, chat model initialization, tool binding, structured output, and middleware. Use for a single-agent tool-calling loop with a system prompt and a fixed tool list; use langgraph-code instead when the task needs explicit multi-step state-machine control f

• langgraph-code

  Build stateful, multi-actor LangGraph agents in Python — StateGraph definition, conditional routing, checkpointing/persistence, and human-in-the-loop interrupts. Use when a task needs explicit multi-step control flow, crash/interrupt recovery, or approval gates — not for a single-turn prompt or a si

• pe-ic-memo

  Draft a private equity investment committee memo and render it as a branded PowerPoint deck. Adapted from the installed private-equity vertical's ic-memo skill (same 9-section structure), with PPTX output instead of Word. Use when preparing IC materials, writing up a deal, or creating a formal recom

• pinning-down-behavior

  Use when checking-coverage-before-change reports an UNCOVERED symbol you must edit — writes characterization (pin-down) tests at the nearest observable seam and verifies they bite before any production edit. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a po

• plan-review-loop

  [Internal discipline — invoked by /brd, /spec, /design, and /test at their human gates; direct use is a power-user path.] Run the human review of a planning artifact as a brainstorming dialogue rather than an approve/reject prompt, and record the rounds so downstream phases can gate on the result.

• portfolio-rollup

  Aggregate per-repo compliance attestations into one integrity-hashed portfolio rollup — verifying each attestation's sha256 integrity, recording an unattested repo as a compliance gap, and computing harness-version drift across the fleet. Use over a local collection directory of attestations, or wit

• pr-respond

  Respond to CI failures and review comments on a harness-opened PR — poll, classify, fix, push, reply with evidence. Bounded and budget-metered; merge stays human-owned. Use when a harness PR shows red CI or unanswered review comments.

• prd

  Author the PRD that starts the pipeline — a collaborative dialogue that produces the id'd requirement spine, the deny-list, and one observable postcondition per requirement. Use before /build, /brd --prd, or any --autonomous run.

• promote

  Use after /retro --apply-decisions to open a PR for one approved recommendation. Never merges. Refuses gate-loosen and security-class items.

• provision

  Provision the GitHub security-compliance gates and verify they hold. Three modes — protection (branch-protection ruleset so gitleaks+sast+code-owner review block merges), environments (deploy-approval environment so a deploy pauses for a required reviewer), fleet (retrofit BOTH gates across many rep

• react-code

  Build client-side React apps with Vite — useEffect cleanup and stale-closure bugs, dependency-array gotchas, Context vs. server-state libraries for API data, Vite environment variables, and testing with Vitest. Scoped to Vite+React client-side apps — NOT Next.js (App Router/Server Components/Server

• refactor

  Refactor existing code for quality, performance, or maintainability. Enforces core quality principles with ratchet gate.

• retro

  Use after /auto or /gate to recommend harness (not product) improvements. Interactive only — does not apply changes.

• reuse-or-justify

  Use when reuse-scout fires at intake (band ≥ medium, a touched constitution invariant, or a same-release clone cluster) — run the confidence-gated reuse-vs-new dialogue and record the decision + performance budget before code. [Internal discipline — invoked by /change, /feature, and /sprint intake;

• scaffold-upgrade

  Upgrade harness control-plane files (hooks, scripts, git-hooks, agents) in a previously scaffolded project without wiping project-manifest or state. Dry-run by default.

• seam-finder

  [Internal pipeline stage — run by /brownfield --seams; invoke directly only as a power user.] Identify the safest cut-points in an existing codebase for a planned change. Reads code-graph.json + a goal, ranks candidate seams by observability + funnel + read/write asymmetry, and outputs a prioritized

• spec-render

  [Internal pipeline stage — dispatched by /spec after its decisions gate passes; invoke directly only to re-render an already-approved decisions file.] Expand an approved spec-decisions.json into the story graph: story files, typed dependency edges, ownership clusters, features.json and the trace spi

• spec

  [Internal pipeline stage — run by /build; invoke directly only as a power user.] Shape the decomposition with the human — milestone scope, epic boundaries, real-vs-defensive dependencies — then dispatch spec-render to expand those decisions into the story graph.

• sprint

  PRD-per-sprint evolution route for an existing harness-built (or brownfield) system — grounds a new PRD against the prior requirement spine, produces a human-approved design amendment against the living specs/design/ baseline, then runs /auto. Companion to /build (sprint 1) and /feature (single-stor

• sprouting-instead-of-editing

  Use when a symbol that must change is UNCOVERED and unpinnable (seam score < 0.5, or a skeletons/-flagged god file with no clean boundary) — adds behavior in a new fully-tested unit instead of editing legacy code in place. [Internal discipline — applied automatically by pipeline agents mid-task; dir

• status

  Show SDLC pipeline progress — a one-shot snapshot, a live watch, or a step timeline. Read-only; aggregates the state the harness already writes. CLI-friendly (Devin-style status/watch/timeline with --json).

• story-sync

  Sync refactor-only code changes back into story bundles and the REASONS Canvas. Use after /implement, /change, or /refactor when owned files moved and acceptance criteria did not. Fails closed if ACs drifted — update the story and run bundle-write instead.

• tracker-publish

  Publish approved Claude Harness dependency groups to Linear/Jira-compatible tracker tasks and write the local tracker mapping contract.

• upgrading-dependencies

  Use when bumping a dependency version — package.json, pyproject.toml, requirements, or lockfile changes — in an existing codebase. Classifies the bump, audits the usage surface from the code graph, and isolates the upgrade in its own proven commit.

• vibe

  Controlled small-change lane for low-risk fixes, docs, tests, and narrowly scoped edits without running the full SDLC pipeline.

• writing-acceptance-tests-first

  Use when a story is about to move from ACs to implementation — write the AT at a Ports-and-Adapters seam and confirm it fails for the right reason. [Internal discipline — applied automatically by pipeline agents mid-task; direct use is a power-user path.]

Slash commands (3)

• /claude_harness_eng_v6:references:scaffold-generation
• /claude_harness_eng_v6:references:scaffold-wizard
• /claude_harness_eng_v6:scaffold

  Initialize a new project with the Claude Harness Engine v5 scaffold.

Subagents (10)

• advisor

  Frontier mid-run advisor. Structural re-rank / unblock / design pivot at fixed checkpoints. Read-only; never implements.

• code-reviewer

  Fresh-context review of a diff or changed-file set for both structure (SOLID breaks, duplication, god functions, hardcoded values, swallowed errors, speculative abstraction) and correctness (logic errors, missing edge cases, contract breaks). Reads only the diff and the files it touches, never the b

• codebase-explorer

  Read-only codebase exploration agent. Maps subsystems, traces dependencies, and reports findings without modifying any files. Use for brownfield discovery, architecture audits, and pre-change impact analysis.

• design-critic

  GAN counterpart for frontend quality. Takes screenshots and scores against 4 criteria (design quality, originality, craft, functionality).

• evaluator

  Skeptical verifier. Runtime mode runs the app and checks sprint-contract criteria (API + Playwright + schema). Artifact mode scores planning documents (BRD, spec, test plan, design, brownfield, seam, deploy) against a rubric. Never generates — only evaluates.

• generator

  Implements code and tests from user stories. Spawns agent teams for parallel execution. Does not rewrite frozen sprint contracts.

• implementer

  Implementation worker for a SINGLE story, spawned by the generator (lead) as a team-mode teammate. Use as the subagent_type when the generator fans out one teammate per story: it implements under quality.test_discipline (outcomes default; tdd / at-first when the manifest says so) under strict file o

• modularity-reviewer

  Inferential modularity review grounded in the deterministic coupling data. Reads specs/brownfield/modularity-pack.md (hubs, cycles, duplication candidates) and judges each against the source — semantic duplication, misplaced responsibility, argument clumps, and whether a high-fan-in module is a real

• planner

  Expands user prompts into BRD, decomposes into stories with dependency graph, designs system architecture, generates feature list and machine-readable schemas.

• security-reviewer

  Scans for injection, auth bypass, hardcoded secrets, SSRF, path traversal, and other OWASP top 10 vulnerabilities. Reviews only the changed-file set of a diff — the review context pack, the touched files, and their immediate data-flow neighbors — never Grepping across all source files. Complements c