
skraft-plugin
Specialized agents, adversarial reviewers, discipline skills (Outside-In TDD, Clean Architecture) and mechanical guardrails (hooks) for Claude Code and GitHu…
Install with your AI
Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.
Install and set up skraft-plugin (claude-plugin project) into my current project. Found on https://claudeers.com/skraft-plugin Repo: https://github.com/SebastienDegodez/skraft-plugin Homepage/docs: https://sebastiendegodez.github.io/skraft-plugin/ Detected install method: claude-plugin → /plugin install skraft-plugin@SebastienDegodez/skraft-plugin Category: plugins. Platforms: cli, api. Read the repo's README for exact setup and env vars, then install it and wire it into my project. Claudeers Health Verdict: active; community-verified: false. Confirm the source before running anything.
/plugin marketplace add SebastienDegodez/skraft-plugin /plugin install skraft-plugin@SebastienDegodez/skraft-plugin
git clone https://github.com/SebastienDegodez/skraft-plugin
// compatibility
| Platforms | cli, api |
|---|---|
| Operating systems | — |
| AI compatibility | claude |
| License | GPL-3.0 |
| Pricing | open-source |
| Language | JavaScript |
skraft
Deterministic agentic SDLC pipeline — backlog discovery and planning, then RESEARCH → DESIGN → DISTILL → DELIVER
Specialized agents, adversarial reviewers, discipline skills (Outside-In TDD, Clean Architecture) and mechanical guardrails (hooks) for Claude Code and GitHub Copilot.
Description
skraft turns a coding assistant into a disciplined software production line.
Each lifecycle phase is driven by a specialized agent, reviewed by a dedicated adversarial
reviewer, and locked down by deterministic guardrails (hooks) that block — before paying
for the sub-agent — any out-of-sequence dispatch, any mandatory skill left unloaded, or any
progression without a real artifact, an APPROVED verdict and a verified git commit.
The runtime core follows a hexagonal architecture (Clean Architecture) with zero external dependency, tested boundary-to-boundary and hardened with mutation testing.
Key features
- 🔁 5-phase SDLC pipeline orchestrated by
skraft-orchestrator: DISCOVER → DISCUSS → DESIGN → DISTILL → DELIVER. - 🤖 Specialized phase agents:
solution-architect,acceptance-designer,software-engineer— each with its dedicated adversarial reviewer;backlog-discovererandbacklog-plannership in the separateskraft-backlogplugin, reviewed by their own lenses. - 🔬 Independent reviewer lenses (quality-gates, architecture-boundaries, test-integrity, cold-reader) synthesized into a weighted verdict.
- 📚 Discipline skills: Outside-In TDD, Clean Architecture testing, BDD/Gherkin, mutation testing, contract testing, ADR, issue refinement…
- 🛡️ Mechanical guardrails G1–G9 (fail-closed hooks): dispatch ordering, forced skill loading + JSONL audit, artifact/verdict/commit verification, state protection, complete handoff of recorded inputs.
- 🎯 Harness-specific packaging: shared sources with native adapters; validation limits in docs/architecture.md.
- 💸 Token economy: state write-through model (rehydration once per session), model routing by cost class, structural phase pruning from confirmed upstream evidence.
Installation
skraft ships as a marketplace plugin. The plugin source lives in plugins/.
Claude Code
Enter these commands in Claude Code:
/plugin marketplace add SebastienDegodez/skraft-plugin
/plugin install skraft
/plugin install skraft-backlog
skraft is the engineering pipeline. skraft-backlog (optional) triages GitHub issues and
refines them into the stories the pipeline reads; see its README.
If Windows fails during /plugin marketplace add with fatal: unable to checkout working tree,
clone SKRAFT to a short local path, then add that checkout as marketplace instead:
git clone https://github.com/SebastienDegodez/skraft-plugin C:\s\skraft
/plugin marketplace add C:\s\skraft
/plugin install skraft
Or enable Windows long paths, restart shell, then retry:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name LongPathsEnabled -Value 1 -PropertyType DWORD -Force
git config --global core.longpaths true
GitHub Copilot, Codex, Cursor
plugins/skraft-framework/plugin.json is the canonical
Agent Plugins v1 manifest, with $schema and no root
agents list. Exactly two editable runtime trees ship: 31 flat Copilot .agent.md
descriptors in com.github.copilot/agents/, and 31 flat native Claude .md descriptors
in com.anthropic.claude-code/agents/. Body and description sync bidirectionally;
Markdown destinations adapt to each client while native headers remain untouched.
Shared-field baseline v2 records stable IDs, not a third descriptor source.
Skills and runtime stay shared.
Hooks have one canonical source, two physical plugin surfaces, with no extra manifest pointers:
| Surface | Hook manifest |
|---|---|
| Canonical source; Claude compatibility | plugins/skraft-framework/hooks/hooks.json |
Generated Copilot namespace; copy with ${PLUGIN_ROOT} | plugins/skraft-framework/com.github.copilot/hooks/hooks.json |
| Separate repository-checkout integration | .github/hooks/skraft-framework.json |
Actual Copilot CLI 1.0.83 fixture tests passed namespaced agent discovery and SessionStart /
PreToolUse with CLAUDE_PLUGIN_ROOT, including paths with spaces.
scripts/copilot-hook-smoke.mjs, run with exact CLI 1.0.83
pinned via --cli and an isolated COPILOT_HOME, also passed against the current migrated
plugin installed from the local marketplace checkout: PASS allowed (1 hook audit entry),
PASS denied (1 hook audit entry), forbidden write absent. This does not verify the full
six-root picker or hidden-subagent invocation.
VS Code 1.126 source currently falls back through .plugin then
.claude-plugin; full live v1 validation remains unverified. These results are not a blanket
compatibility claim. See docs/architecture.md
for current packaging, Claude registration requirements and validation limits.
Quick start
Once the plugin is installed, select skraft-orchestrator in the agent picker
and give it a refined story.
The orchestrator automatically resumes from the last persisted state, manages phase transitions, reviewer verdicts (with retry), and the engineer ↔ reviewer loop.
Documentation
All documentation lives in docs/.
| Topic | Link |
|---|---|
| 📑 Documentation index | docs/README.md |
| 🏗️ Plugin architecture | docs/architecture.md |
| 🔌 Distributed plugin (install, pipeline, guardrails, packaging) | plugins/skraft-framework/README.md |
| 🛣️ Roadmap (13 US + status) | docs/roadmap.md |
| 🤝 Engineer/Reviewer cross-cutting view | docs/agents/software-engineer-and-reviewer.md |
| 🎨 Documentation conventions | docs/conventions.md |
Current status — summary
| Component | Status |
|---|---|
SDLC pipeline orchestrated by skraft-orchestrator | ✅ Implemented |
Specialized phase agents (backlog-*, solution-architect*, acceptance-designer*, software-engineer*) | ✅ Implemented |
Reviewer lenses (quality-gates, architecture-boundaries, test-integrity, cold-reader) | ✅ Implemented |
Operational skills (plugins/skraft-framework/skills/*) | ✅ Implemented |
| Runtime guardrails G1–G9 (hooks; G4/G5 in the state CLI) | ✅ Implemented and tested; live harness receipt for G7 only |
Observability (health check, housekeeping) and recovery (diagnose, rollback, resolve-stale) | ✅ Implemented — see the roadmap |
Development
Edit only canonical agent and hook sources, then run npm run plugin:build and
npm run plugin:check to generate and verify Copilot adapters. Commit generated adapters:
marketplace Git installs do not run a build.
# Tests (boundary-to-boundary, 0 runtime dependency)
node --test "tests/skraft-framework/**/*.test.mjs"
# Mutation testing (Stryker)
npm --prefix plugins/skraft-framework/src ci && node plugins/skraft-framework/src/node_modules/.bin/stryker run plugins/skraft-framework/src/stryker.config.mjs
# Policy checks (data-driven config, models by cost class)
node plugins/skraft-framework/src/cli/build-config-bin.mjs --check
node plugins/skraft-framework/src/cli/resolve-model-bin.mjs --check
Test placement and Stryker configuration rules are described in AGENTS.md.
Versioning & releases
This project follows SemVer and publishes releases automatically via semantic-release.
- Commit messages must follow Conventional Commits:
feat:→ minor bump;fix:/perf:/refactor:→ patch bump;feat!:or aBREAKING CHANGE:footer → major bump.
docs:never cuts a tag — whatever the scope. Documentation lands without a version, and a docs-only push does not even start the workflow (paths-ignore). Adocs:commit riding along with afeat:orfix:is released by that commit, as expected.- The
release.ymlworkflow runs automatically on every push tomain, and can also be started by hand from the Actions tab. When it runs, it:- computes the next version from the commit history,
- updates CHANGELOG.md and stamps plugin manifests and runtime package metadata through scripts/set-version.mjs,
- creates the
vX.Y.Ztag and the GitHub Release with the release notes, - commits everything with
chore(release): X.Y.Z [skip ci].
See the Releases for the per-version change history.
Contributing
- Branch off
main. - Use Conventional Commits (required for automatic versioning).
node --test "tests/skraft-framework/**/*.test.mjs"must pass.- Open a Pull Request — CI checks tests, config policy and models.
License
GNU General Public License v3.0 or later (GPL-3.0-or-later) — full text in LICENSE.
Copyright (C) 2026 Degodez Sébastien
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. It is distributed WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
// faq
What is skraft-plugin?
Specialized agents, adversarial reviewers, discipline skills (Outside-In TDD, Clean Architecture) and mechanical guardrails (hooks) for Claude Code and GitHub Copilot.. It is open-source on GitHub.
Is skraft-plugin free to use?
skraft-plugin is open-source under the GPL-3.0 license, so it is free to use.
What category does skraft-plugin belong to?
skraft-plugin is listed under plugins in the Claudeers registry of Claude-compatible tools.
// embed badge
[](https://claudeers.com/skraft-plugin)
// retro hit counter
[](https://claudeers.com/skraft-plugin)
// reviews
// guestbook
// related in Claude Plugins
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explainin…
"CLI-Anything: Making ALL Software Agent-Native" -- CLI-Hub: https://clianything.cc/
financial-services — a Claude ecosystem project on GitHub.