By komluk Verified
11 agents, 33 skills, 16 commands, 9 hooks - spec-driven multi-agent orchestration for Claude Code, with optional cross-device semantic memory.
Archive a completed change in the experimental workflow
Analyze and optimize Claude Code's context configuration (analyze, optimize, or reset).
Scaffold a new scaffolding-compatible skill: an interactive flow that creates
Health-check the scaffolding install and report install problems plus exact fixes (diagnose-only, never mutates).
Initialize OpenSpec in a project directory with the scaffolding-workflow schema.
Analyzes tasks and decomposes them into a sequence of agent steps for execution.
Requirements analyst. MUST BE USED for ambiguous requests, requirements gathering, scope assessment, feasibility checks, and proposal writing. NOT for small, clearly-scoped changes (those go directly to developer). PROACTIVELY interprets user intent and produces proposal.md specs.
Technical architect. MUST BE USED for system design, API design, implementation planning, multi-file refactoring, and agent orchestration. Receives proposal.md from analyst and produces design.md + tasks.md.
Bug investigation specialist. MUST BE USED for bug reports, unexpected behavior, error diagnosis. PROACTIVELY performs systematic root cause analysis using progressive debugging techniques.
Expert software engineer. Use proactively to implement features, fix bugs, write tests, style UI, and make code changes. MUST BE USED for all development tasks. Direct target for small, clearly-scoped changes — no analyst/architect needed first.
GitHub Actions CI pipeline templates and workflow YAML patterns. TRIGGER when: creating or editing a CI workflow, adding a CI job, or wiring build/test/deploy steps. SKIP: container build internals (use docker-templates); local git workflow (use git-operations).
Write OpenSpec design.md and tasks.md artifacts. TRIGGER when: producing a technical design or task checklist for a spec-driven feature. SKIP: writing proposal.md (use spec-research); executing tasks.md (use spec-develop).
Execute an OpenSpec tasks.md during implementation. TRIGGER when: working through spec task checkboxes and applying code changes. SKIP: authoring the tasks.md (use spec-design); verifying the result (use spec-review).
Monitoring, metrics, alerting, and observability standards. TRIGGER when: implementing health checks, collecting metrics, or defining alert rules. SKIP: log statement formatting (use logging-standards); CI pipeline setup (use github-actions-template).
Structured logging standards: log levels, structured fields, correlation IDs, PII masking, and event naming. TRIGGER when: adding log statements, configuring loggers, or reviewing log output. SKIP: metrics and alerting (use monitoring-observability); error control flow (use error-handling). (Examples use structlog + an OTLP sink.)
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Verified owner:Łukasz Komosa
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Portable Claude Code configuration: 13 agents, 35 skills, 19 commands, 15 hooks, spec-driven workflows. Installs as a Claude Code plugin.
claude-scaffolding is a portable, markdown-only Claude Code configuration. It
provides multi-agent orchestration, a library of reusable skills, guardrail
hooks, and spec-driven workflows — everything ships as plain markdown and runs
entirely on the Claude Code runtime, with no backend, database, or
long-running process required.
/create-skill scaffolds your own scaffolding-compatible skills, and /learn closes the loop by distilling reusable insights from finished conversations.Everything below is opt-in or default-safe — existing installs behave exactly as before until you set a flag or invoke a new agent. See the CHANGELOG for the full list.
prompt-engineer (system prompts,
guardrail rules, prompt evals, LLM-judge rubrics, injection defense) and
mcp-builder (design/build/test MCP servers, tool schemas, transport, auth
launchers).auto-init-check), opt-in
auto-format (post-edit-format), opt-in desktop/terminal notifications
(notify), opt-in completion nudge (completion-nudge), a hard block on the
general-purpose/explore subagents (block-subagent), and a warn-only
500-line file check (
file-size-warn).
analyst, architect, and reviewer declare
model: opus + effort: high; developer stays inherit. The reviewer on a
higher tier breaks same-model self-review and records a cross_model flag in
its report. The plugin emits only literal sonnet/opus/haiku; backend
mapping lives on the aiproxy/litellm side — see docs/model-tiers.md./init-rules command: scaffolds opt-in, path-scoped nested CLAUDE.md
rule files so per-area conventions lazy-load only where relevant, while routing
stays always-loaded.<important>, and
forced delegation softened so trivial Q&A may be answered directly while real
engineering work is still delegated.context: fork on four heavy skills (ui-ux-pro-max,
mui-styling, logging-standards, monitoring-observability) and
!`command` dynamic injection in the git/worktree/context-engineering skills.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
— see docs/agent-teams.md.All flags are off by default; the plugin's behavior is unchanged unless you set them.
| Flag | Default | Effect |
|---|---|---|
SCAFFOLDING_AUTOFORMAT | off | =1 enables post-edit-format.sh — auto-formats the single edited file (ruff/black, prettier, dotnet format); never blocks. |
SCAFFOLDING_NOTIFY | off | =1 enables notify.sh — desktop/terminal notification on turn-finish or input-needed. |
SCAFFOLDING_COMPLETION_NUDGE | off | =1 advisory nudge to finish the delegation chain; =block enforces it (loop-guarded). |
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS | off | =1 enables the experimental agent-teams mode (see docs/agent-teams.md). |
npx claudepluginhub komluk/scaffolding --plugin scaffoldingGeneric agent harness for Claude Code — pipeline agents, skills, continuation hook, plus the engine setup (re-run per update).
Multi-agent orchestration system for Claude Code
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation
Multi-agent /workflow development pipeline (planner → plan-review → coder → code-review) with typed handoff contracts, lifecycle hooks, and MCP servers.
Harness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.