Forge
Skill19 starsChanged 9 months agoMITView on GitHub
Forge: SVK Skill Builder. A 5-phase pipeline for building SVK skills with automated convention enforcement and shipping checklist validation. Run /Forge:brainstorm to start designing a new skill.
79 other projects use a version of this.
Adopted by
Most recently taken up by
- stericishere/skillstheir own version, first seen Nov 15, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- faizanio/FORGEtheir own version, first seen Nov 8, 2026
- jeanchristoph/claude_forgetheir own version, first seen Nov 6, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Nov 6, 2026
- rmkr/skillstheir own version, first seen Nov 5, 2026
Used with
Projects with it also use forge-ship, forge-review and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
redteamlifeSkillforge-ship
Use when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.
Also in 6 projects that use this
tonmoy007Skillforge-review
Run a multi-dimensional parallel code review over the current change.
Also in 8 projects that use this
weselbenSkillforge-docs
Load before code changes, before writing docs or an ADR, when a user question exposes a missing how-to, and when closing a chunk of work; also loaded by forge after each squash-merge and by deep-research after a report.
Also in 3 projects that use this
DailenGSkillforge-design
Design, UX, and polish discipline for the forge lifecycle. Covers the design tier, the design brief in docs/DESIGN.md, UX requirements and their verification methods, the per-slice design pass, the UX defect register, and the release polish pass. Load whenever work touches a user-facing surface (GUI, terminal, library API, or operated service), whenever a UX observation needs disposing of, and whenever a release is in reach.
Also in 3 projects that use this
DshamirSkillforge-plan
Takes analysis.json + budget cap → derives the full phase sequence, hyperparameters, instance type, cost estimate, and acceptance thresholds. Emits plan.md (the single human gate document) and plan.json (the machine-readable spec that dispatch-v2 consumes). Refuses to plan if estimated cost exceeds budget×1.2.
Also in 4 projects that use this
tonmoy007Skillforge-build
Run Stage 6 of the Forge pipeline — implementation. Use when the user says
Also in 3 projects that use this
Other versions79 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 79
- cwinvestments/memstack★ 425same name
- ansari-project/codev★ 298same name
- cluesmith/codev★ 298same name
- swyxio/skills★ 194same name
- simota/agent-skills★ 96same name
- alp82/forge★ 36same name
- TT-Wang/forge★ 34same name
- emiliosheinz/agent-skills★ 20same name
- kecoma1/MQL5-SKILLS★ 17same name
- yz5e/agent-skills★ 17same name
69 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 68 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Look for .claude/svk-meta.json in the current project.
- Very specific: line 26
Read the svk_repo path and installed_version from the metadata file.
- Very specific: line 28
Run: git -C <svk_repo> tag --sort=-v:refname | head -1 to get the latest tag.
- Distinctive: line 30
If they match, skip — the user is up to date.
- Distinctive: line 31
If the latest tag is newer, show this message ONCE (never repeat in this session):
- Distinctive: line 37
If the git commands fail (offline, repo moved, etc.), skip silently.
- Distinctive: line 39
Important: Do NOT block or delay the user's actual command.
“Common” is measured: kept by at least 6 in 10 of the 68 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- SVK Version Check — runs once per session on first skill invocation --><svk-version-check>
**On first invocation this session**, silently perform a version check:- Look for
.claude/svk-meta.jsonin the current project. If it doesn't exist, skip this check entirely. - Read the
svk_repopath andinstalled_versionfrom the metadata file. - Run:
git -C <svk_repo> fetch --tags --quiet 2>/dev/null - Run:
git -C <svk_repo> tag --sort=-v:refname | head -1to get the latest tag. - Compare the installed version against the latest tag (strip the leading
v). - If they match, skip — the user is up to date.
- If the latest tag is newer, show this message ONCE (never repeat in this session):
SVK Update Available: v{latest} is available (you're on v{installed}).
- Update now: I can pull and reinstall the changed skills in this session
- Update later: Start a new chat and run
/SVK:update
- If the git commands fail (offline, repo moved, etc.), skip silently. Never show errors from version checking.
Important: Do NOT block or delay the user's actual command. Perform this check, show the notification if needed, then proceed with the command they invoked.
</svk-version-check>
Forge — SVK Skill Builder
A meta-skill for building SVK skills. Wraps Superpowers skills with SVK-specific context injection and enforces a 21-item shipping checklist.
Commands
| Command | Description |
/Forge:brainstorm | Phase 1 — Design a new skill (wraps superpowers:brainstorming) |
/Forge:plan | Phase 2 — Write implementation plan (wraps superpowers:writing-plans) |
/Forge:build | Phase 3 — Execute the plan with scaffolding (wraps superpowers:executing-plans) |
/Forge:validate | Phase 4 — Two-pass validation against shipping checklist |
/Forge:ship | Phase 5 — Commit, test install, and clean up |
Pipeline
/Forge:brainstorm → /Forge:plan → /Forge:build → /Forge:validate → /Forge:shipEach phase is a separate command. You can enter at any phase if you already have the prerequisite artifacts (e.g., skip brainstorm if you have a design doc). Validate and ship enforce the full checklist regardless.
Resources
Load resources from resources/INDEX.md when needed — don't read them all upfront.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

