jeanclaudevibedan

Open Scaffold — AI skill for Claude Code

AI community

Repo-native work record for AI-assisted work: plans, evidence, human gates, and clean agent handoffs.

How to install Open Scaffold

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jeanclaudevibedan/open-scaffold and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Open Scaffold does

Repo-native work record for AI-assisted work: plans, evidence, human gates, and clean agent handoffs.

Alternatives in AI

  • Konnect — AI-assisted PCB design for KiCAD 10. Native KiCAD plugin — a single Rust binary exposing 171 schematic, layout 341 ★
  • Component To Release Agent — Chains design-to-code, accessibility and token-compliance checks (three release gates), then the AI descriptio 194 ★
  • Crab Code — 🦀 Open-source alternative to Claude Code, built from scratch in Rust 74 ★

README

open-scaffold

**Your AI agent's work belongs in your repo, not its chat history.**

Ambient work records, compact handoffs, and bounded review/gate checks from cheap and local models — for AI-assisted work that needs evidence, recovery, and human gates, with pilot-grade proof boundaries.

[![License: MIT](https://img.shields.io/badge/License-MIT-black.svg)](LICENSE) [![npm](https://img.shields.io/npm/v/open-scaffold.svg)](https://www.npmjs.com/package/open-scaffold) [![Works with](https://img.shields.io/badge/Works%20with-Any%20agent-green.svg)](#vendor-neutral-by-design) [![Runtime deps](https://img.shields.io/badge/Runtime%20deps-Zero-blue.svg)](package.json)

The problem

You pay frontier prices for review, status checks, and "where were we" because nothing cheaper can be trusted. Cheaper models guess; when a chat ends, the work's memory dies with it; the next session reconstructs from a scrollback buffer and invents what it can't recover.

What it does

Open Scaffold keeps a repo-native work record — git-tracked, observed-fact files about what your agents did — and turns it into three things:

  • Record (ambient). Extracted from observed facts — transcripts, receipts, test results — costing the working model nothing. osc capture --from claude-code|codex reads a finished session into a record with no worker cooperation. Add a plan and evidence files to check claims against intent; feedback and lessons carry forward instead of being relearned.
  • Handoff. osc handoff compiles the record into a budgeted, secret-redacted packet so the next reader — a fresh session, a smaller model, another vendor's agent, or a teammate — resumes from truth instead of re-deriving or inventing it.
  • Review and gate. osc review reports plateaus, failing criteria, and requirements worth questioning; osc gate turns that into a retry authorization with stop authority outside the worker. Any file-reading model can be the judge. Fails