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
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Verified owner:Łukasz Komosa
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.