Gsd Phase
open-gsd/gsd-core
Multi-phase management — add, insert, remove, or edit phases in ROADMAP.md (roadmap phase CRUD)
Evidence-based phase completion enforcement for /dev:feature.
$ npx skills add MadAppGang/claude-code --skill phase-enforcement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MadAppGang/claude-code phase-enforcement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/dev/skills/enforcement .claude/skills/phase-enforcement && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "phase-enforcement" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/dev/skills/enforcement into .claude/skills/phase-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phase-enforcement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MadAppGang/claude-code/tree/main/plugins/dev/skills/enforcementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MadAppGang/claude-code --skill phase-enforcement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MadAppGang/claude-code phase-enforcement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/dev/skills/enforcement .agents/skills/phase-enforcement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "phase-enforcement" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/dev/skills/enforcement into .agents/skills/phase-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phase-enforcement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MadAppGang/claude-code --skill phase-enforcement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MadAppGang/claude-code phase-enforcement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/dev/skills/enforcement .cursor/skills/phase-enforcement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "phase-enforcement" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/dev/skills/enforcement into .cursor/skills/phase-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phase-enforcement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MadAppGang/claude-code.git --path plugins/dev/skills/enforcement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MadAppGang/claude-code --skill phase-enforcement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MadAppGang/claude-code phase-enforcement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/dev/skills/enforcement .gemini/skills/phase-enforcement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "phase-enforcement" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/dev/skills/enforcement into .gemini/skills/phase-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phase-enforcement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MadAppGang/claude-code phase-enforcementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MadAppGang/claude-code --skill phase-enforcement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/dev/skills/enforcement .github/skills/phase-enforcement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "phase-enforcement" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/dev/skills/enforcement into .github/skills/phase-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phase-enforcement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MadAppGang/claude-code --skill phase-enforcement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MadAppGang/claude-code phase-enforcement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/dev/skills/enforcement .opencode/skills/phase-enforcement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "phase-enforcement" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/dev/skills/enforcement into .opencode/skills/phase-enforcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phase-enforcement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
phase-enforcementEvidence-based phase completion enforcement for /dev:feature.
Phase Enforcement is an agent skill from MadAppGang/claude-code. Evidence-based phase completion enforcement for /dev:feature. Use when orchestrating 8-phase feature development to ensure artifacts exist before phase completion, validation criteria are addressed, outer loops are enforced, and show-your-work requirements are met.
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: claude code plugins marketplace. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
nodeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Phase Enforcement loads about 3.4k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 646 words, ~3,424 tokens.
.claude/skills/phase-enforcement/SKILL.md (or your agent's skills folder).Version: 1.0.0 Purpose: Mechanical enforcement of phase completion requirements for /dev:feature Status: Production Ready
This skill provides mechanical enforcement (not just prompt-based instructions) for the 8-phase feature development workflow. It prevents:
Script: scripts/phase-completion-validator.js
How it works:
Required Artifacts per Phase:
| Phase | Required Artifacts | Custom Checks |
|---|---|---|
| 1 | requirements.md, validation-criteria.md, iteration-config.json | Config has required fields |
| 3 | architecture.md | Plan reviews exist |
| 4 | implementation-log.md | Git changes detected |
| 5 | reviews/code-review/consolidated.md | Has PASS/FAIL verdict |
| 6 | tests/test-plan.md | Test files created |
| 7 | validation/result.md | Has PASS/FAIL status + evidence |
| 8 | report.md | Phase 7 PASSED |
Usage in orchestrator:
Before marking any phase complete:
1. Run checkpoint verification:
```bash
${PLUGIN_PATH}/scripts/checkpoint-verifier.sh phase{N} ${SESSION_PATH}If check passes, mark task complete:
TaskUpdate(taskId: X, status: "completed")If check fails, DO NOT mark complete. Fix missing artifacts first.
---
### 2. Outer Loop Enforcer
**Script:** `scripts/outer-loop-enforcer.js`
**How it works:**
- Tracks iteration state in session-meta.json
- Blocks Phase 8 unless Phase 7 PASSED
- Detects regression (score getting worse)
- Handles escalation when max iterations reached
**Commands:**
```bash
# Start new iteration (call before Phase 3)
node outer-loop-enforcer.js start-iteration ${SESSION_PATH}
# Record Phase 7 result
node outer-loop-enforcer.js record-result ${SESSION_PATH} PASS "All checks passed" 95
# Check if Phase 8 can proceed
node outer-loop-enforcer.js check-can-complete ${SESSION_PATH}
# Get current status
node outer-loop-enforcer.js get-status ${SESSION_PATH}Session state tracking:
{
"outerLoop": {
"currentIteration": 2,
"maxIterations": 3,
"mode": "limited",
"phase7Results": [
{"iteration": 1, "status": "FAIL", "reason": "Button color mismatch", "score": 78},
{"iteration": 2, "status": "PASS", "reason": "All checks passed", "score": 94}
]
}
}Usage in orchestrator:
OUTER LOOP: Before starting Phase 3
1. Start iteration:
```bash
node ${PLUGIN_PATH}/scripts/outer-loop-enforcer.js start-iteration ${SESSION_PATH}OUTER LOOP: After Phase 7 completes
Record result:
node ${PLUGIN_PATH}/scripts/outer-loop-enforcer.js record-result ${SESSION_PATH} <PASS|FAIL> "reason" [score]If PASS: Proceed to Phase 8
If FAIL: Loop back to Phase 3 (start-iteration will be called again)
OUTER LOOP: Before Phase 8
Verify Phase 7 passed:
node ${PLUGIN_PATH}/scripts/outer-loop-enforcer.js check-can-complete ${SESSION_PATH}If exit code 1: BLOCKED - cannot proceed to Phase 8
---
### 3. Validation Criteria Enforcer
**Script:** `scripts/validation-criteria-enforcer.js`
**How it works:**
- Parses validation-criteria.md from Phase 1
- Parses validation/result.md from Phase 7
- Matches criteria to results using fuzzy matching
- Blocks if >20% criteria unaddressed
**Usage in orchestrator:**
```markdown
PHASE 7: After creating result.md
1. Run criteria enforcer:
```bash
node ${PLUGIN_PATH}/scripts/validation-criteria-enforcer.js ${SESSION_PATH}Review generated report: ${SESSION_PATH}/validation/criteria-mapping.md
If unaddressed criteria found:
**Output format:**
```markdown
# Validation Criteria Mapping Report
## Summary
- Total Criteria: 5
- Matched: 4
- Unmatched: 1
- Coverage: 80%
## Criteria Mapping
| Line | Criterion | Result | Evidence |
|------|-----------|--------|----------|
| 12 | "Navigate to test URL" | PASS | screenshot-before.png |
| 13 | "Fill email field" | PASS | action-log.md line 5 |
| 14 | "Click login button" | PASS | action-log.md line 8 |
| 15 | "Redirect to dashboard" | PASS | screenshot-after.png |
## ⚠️ Unaddressed Criteria
- Line 16: "Show error for invalid password"Script: scripts/checkpoint-verifier.sh
How it works:
Usage:
# Before completing Phase 4
./checkpoint-verifier.sh phase4 ${SESSION_PATH}
# Before completing Phase 7
./checkpoint-verifier.sh phase7 ${SESSION_PATH}Example output:
📋 Checkpoint Verification: phase4
─────────────────────────────────────
Session: ai-docs/sessions/dev-feature-login-20260204-143022
✅ Implementation Log: implementation-log.md (1234 bytes)
✅ Code Changes: 8 files with changes
✅ Implementation Log: Has structured progress
─────────────────────────────────────
✅ Checkpoint passedMANDATORY: Before marking ANY phase as completed:
<phase_completion_protocol>
**Step 1: Run Checkpoint Verification**
```bash
${PLUGIN_PATH}/scripts/checkpoint-verifier.sh phase{N} ${SESSION_PATH}If exit code != 0: STOP. Fix missing artifacts first.
Step 2: Show Evidence Summary
Display 3-5 lines of actual results:
## Phase {N} Evidence
- Artifact: ${SESSION_PATH}/{artifact}.md (exists, 1234 bytes)
- Key result: {actual output from phase}
- Evidence: {file paths to screenshots, logs, etc.}Step 3: Map to Original Criteria (for Phase 7)
From validation-criteria.md:
- [x] Criterion 1 → Verified (evidence file)
- [x] Criterion 2 → Verified (screenshot)
- [ ] Criterion 3 → Skipped (reason documented)Step 4: Mark Task Complete
Only if Steps 1-3 pass:
TaskUpdate(taskId: X, status: "completed")</phase_completion_protocol>
### Show-Your-Work Requirement
**Anti-pattern (BLOCKED):**
```markdown
I'll run the tests now.
[Task tool call to run tests]
Tests passed! Moving to next phase.Required pattern:
Running tests:
$ bun test
✓ auth.test.ts (5 tests)
✓ should authenticate valid user (12ms)
✓ should reject invalid password (8ms)
✓ should expire session after timeout (15ms)
✓ should refresh token correctly (10ms)
✓ should logout user (5ms)
✗ payment.test.ts (3 tests)
✓ should process valid payment (20ms)
✓ should reject invalid card (12ms)
✗ should handle timeout (FAILED)
Error: Expected timeout after 30s, got success
Results: 7 passed, 1 failed
The payment timeout test failure needs investigation before Phase 6 can complete.COMPLETE: All validation criteria passed
PARTIAL: Some validation done, gaps documented
INCOMPLETE: Blocked, needs user action
{
"status": "partial",
"completedCriteria": ["builds", "type-checks", "login-flow"],
"skippedCriteria": [
{"criterion": "full-auth-flow", "reason": "requires running server"},
{"criterion": "token-storage", "reason": "depends on auth flow"}
],
"blockers": []
}## Feature Status: PARTIAL
### Completed ✓
- SDK implementation
- Type safety
- Build verification
### Not Verified ⚠️
- End-to-end authentication (requires running server)
- Token storage persistence (depends on auth)
### Recommended Before Production
1. Run integration tests with real server
2. Verify token encryption roundtripScript: scripts/failure-report-generator.js
How it works:
When generated:
Report structure:
# {Phase Name} - Failure Report
**Generated:** 2026-02-04T10:30:00Z
**Session:** ai-docs/sessions/dev-feature-login-20260204
**Phase:** phase7
## Expected Artifacts
- ❌ `validation/result.md`
- ❌ `validation/screenshot-before.png`
- ❌ `validation/screenshot-after.png`
## Attempted Approaches
### Attempt 1: browser_test
**What was tried:** Chrome MCP navigation to localhost:3000
**Error:** Tool mcp__chrome-devtools__navigate_page not available
**Timestamp:** 2026-02-04T10:25:00Z
## Failure Analysis
### Common Failure Reasons
- **chrome_mcp_unavailable**: Chrome MCP tools not available or not responding
- **server_not_starting**: Dev server fails to start
- **page_not_loading**: Test URL not accessible
## Suggestions for Resolution
1. Verify Chrome MCP is properly configured in .claude/settings.json
2. Check if dev server is running: curl http://localhost:3000
3. Try using different browser automation: mcp__claude-in-chrome instead
4. Consider unit tests + manual verification as fallback
## Manual Testing Steps
1. Start dev server: npm run dev (or bun run dev)
2. Open browser to test URL (e.g., http://localhost:3000)
3. Take screenshot of initial state
4. Perform test actions (fill forms, click buttons)
5. Take screenshot of result state
6. Verify expected behavior occurred
7. Document results in validation/result.md
## Workarounds
### If Browser Automation Unavailable
1. Run validation manually in browser
2. Take screenshots with system screenshot tool
3. Save screenshots to `validation/` directory
4. Create `validation/result.md` with manual observations
### Minimal result.md Template
[template provided]
## Next Steps
1. **Fix and Retry**: Address the issues above and re-run the phase
2. **Manual Completion**: Follow manual steps and create artifacts manually
3. **Skip with Justification**: Create `phase7-skip-reason.md` explaining why
4. **Escalate to User**: Ask user for guidance via AskUserQuestionUsage in orchestrator:
When phase completion is blocked:
1. Failure report auto-generated at:
${SESSION_PATH}/failures/phase{N}-failure-report.md
2. Read report and either:
a. Fix issues and retry
b. Follow manual testing steps
c. Create skip-reason.md with justification
d. Escalate to user with AskUserQuestion
3. If manually completing:
- Create required artifacts following templates in report
- Re-run phase completion validator| Enforcement | What It Prevents |
|---|---|
| Phase completion validator | Claiming "done" without proof |
| Mandatory artifacts | Skipping documentation |
| Validation criteria enforcer | Collecting criteria but ignoring them |
| Outer loop enforcer | Skipping retry logic |
| Phase 6 test check | Shipping without tests |
| Graceful degradation | Faking completion when blocked |
| Show-your-work | Hiding actual results |
| Checkpoint verification | Automated sanity checks |
| Failure report generator | Silent failures without guidance |
Scripts Location: ${PLUGIN_ROOT}/plugins/dev/scripts/
Hooks Config: ${PLUGIN_ROOT}/plugins/dev/hooks/feature-enforcement.json
© MadAppGang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/dev/skills/enforcement of MadAppGang/claude-code.
Open the folder on GitHubat commit 6097ad4
Phase Enforcement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Phase Enforcement this skillMadAppGang/claude-code | 285 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Gsd Phaseopen-gsd/gsd-core | 10k | 1 repos | ~603 | Automated safety check: Notes | MIT | |
| Verification Before Completionforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Verification Before Completionfarm-fe/farm | 5.6k | 46 repos | ~1k | Automated safety check: Pass | MIT | |
| Bio Phasing Imputation Haplotype PhasingGPTomics/bioSkills | 1.2k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Performing Dmarc Policy Enforcement Rolloutmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
open-gsd/gsd-core
Multi-phase management — add, insert, remove, or edit phases in ROADMAP.md (roadmap phase CRUD)
foryourhealth111-pixel/Vibe-Skills
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
GPTomics/bioSkills
Estimates haplotype phase from population linkage disequilibrium with SHAPEIT5, SHAPEIT4, Eagle2, or Beagle - turning unphased genotypes (0/1) into phased haplotypes (0|1) for imputation input…
mukul975/Anthropic-Cybersecurity-Skills
Execute a phased DMARC rollout by inventorying sending sources, configuring SPF/DKIM alignment, and progressing DNS policy from p=none monitoring through p=quarantine to p=reject enforcement…
moeru-ai/airi
Enforce AIRI's testing and Vitest practices in the AIRI monorepo.
MadAppGang/claude-code
Content brief template and creation methodology for SEO-optimized content.
MadAppGang/claude-code
A skill your agent uses when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g…
MadAppGang/claude-code
On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.
MadAppGang/claude-code
Techniques for expanding seed keywords and clustering by topic and intent.
MadAppGang/claude-code
SERP analysis techniques for intent classification, feature identification, and competitive intelligence.
MadAppGang/claude-code
A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.
Evidence-based phase completion enforcement for /dev:feature. Phase Enforcement is an agent skill from MadAppGang/claude-code. Evidence-based phase completion enforcement for /dev:feature.
Phase Enforcement fits situations like: orchestrating 8-phase feature development to ensure artifacts exist before phase completion; validation criteria are addressed; outer loops are enforced; show-your-work requirements are met.
Run `npx skills add MadAppGang/claude-code --skill phase-enforcement -a claude-code`. Or copy the skill folder (plugins/dev/skills/enforcement in MadAppGang/claude-code) into .claude/skills/phase-enforcement in your project. Claude Code loads it when a task matches its description.
Run `npx skills add MadAppGang/claude-code --skill phase-enforcement -a codex`. Or copy the skill folder (plugins/dev/skills/enforcement in MadAppGang/claude-code) into .agents/skills/phase-enforcement in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MadAppGang/claude-code --skill phase-enforcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/phase-enforcement, .gemini/skills/phase-enforcement, .github/skills/phase-enforcement and .opencode/skills/phase-enforcement in your project.
Going by SKILL.md and its folder, Phase Enforcement needs the command-line tools its instructions call (node).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Phase Enforcement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Phase Enforcement: Gsd Phase (open-gsd/gsd-core, 10k stars), Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Verification Before Completion (farm-fe/farm, 5.6k stars) and Bio Phasing Imputation Haplotype Phasing (GPTomics/bioSkills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.
Source: MadAppGang/claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.