Agent skill

Phase Enforcement

by MadAppGang in MadAppGang/claude-code

Evidence-based phase completion enforcement for /dev:feature.

MITAuto-check passed

Install Phase Enforcement

skills CLI
$ npx skills add MadAppGang/claude-code --skill phase-enforcement -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MadAppGang/claude-code phase-enforcement --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
phase-enforcement
GitHub stars
285
Token cost
~3.4k tokens
SKILL.md length
646 words
Files
1
Skills in repo
69
Repo updated
First seen
Licence
MIT

At a glance

Evidence-based phase completion enforcement for /dev:feature.

  • Works in 3 steps: Phase Completion Validator → Checkpoint Verifier → Failure Report Generator
  • Orchestrating 8-phase feature development to ensure artifacts exist before phase completion
  • SKILL.md covers Overview, Enforcement Components, Integration with /dev:feature and Graceful Degradation, plus 2 more sections
  • Calls node

What it does

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.

When your agent uses it

  • 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

Example prompts

  • “/phase-enforcement”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Phase Completion Validator
  2. Checkpoint Verifier
  3. Failure Report Generator

What it can do on your machine

Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 646 words, ~3,424 tokens.

Download SKILL.mdSave it as .claude/skills/phase-enforcement/SKILL.md (or your agent's skills folder).
name
phase-enforcement
description
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.
version
1.0.0
tags
orchestration, enforcement, validation, quality-gates, evidence
keywords
phase-completion, artifacts, evidence, validation-criteria, outer-loop, checkpoint, enforcement, quality-gate
plugin
dev
updated
2026-02-04

Phase Completion Enforcement

Version: 1.0.0 Purpose: Mechanical enforcement of phase completion requirements for /dev:feature Status: Production Ready

Overview

This skill provides mechanical enforcement (not just prompt-based instructions) for the 8-phase feature development workflow. It prevents:

  1. Claiming completion without proof - Artifacts must exist
  2. Skipping documentation - Required files per phase
  3. Ignoring validation criteria - Phase 1 criteria must map to Phase 7 results
  4. Bypassing retry logic - Outer loop enforced with state tracking
  5. Shipping without tests - Phase 6 requires test files
  6. Faking completion when blocked - Graceful degradation with honest status
  7. Hiding actual results - Show-your-work requirement
  8. Missing automated checks - Checkpoint verification at boundaries

Enforcement Components

1. Phase Completion Validator

Script: scripts/phase-completion-validator.js

How it works:

  • Runs as PreToolUse hook on TaskUpdate
  • Detects phase from task subject (e.g., "Phase 3: Planning")
  • Checks required artifacts exist for that phase
  • Blocks completion if artifacts missing or empty

Required Artifacts per Phase:

PhaseRequired ArtifactsCustom Checks
1requirements.md, validation-criteria.md, iteration-config.jsonConfig has required fields
3architecture.mdPlan reviews exist
4implementation-log.mdGit changes detected
5reviews/code-review/consolidated.mdHas PASS/FAIL verdict
6tests/test-plan.mdTest files created
7validation/result.mdHas PASS/FAIL status + evidence
8report.mdPhase 7 PASSED

Usage in orchestrator:

markdown
Before marking any phase complete:

1. Run checkpoint verification:
   ```bash
   ${PLUGIN_PATH}/scripts/checkpoint-verifier.sh phase{N} ${SESSION_PATH}
  1. If check passes, mark task complete:

    TaskUpdate(taskId: X, status: "completed")
  2. 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:

json
{
  "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:

markdown
OUTER LOOP: Before starting Phase 3

1. Start iteration:
   ```bash
   node ${PLUGIN_PATH}/scripts/outer-loop-enforcer.js start-iteration ${SESSION_PATH}
  1. Check exit code:
    • 0: Proceed with iteration
    • 2: Max iterations reached, escalate to user

OUTER LOOP: After Phase 7 completes

  1. Record result:

    bash
    node ${PLUGIN_PATH}/scripts/outer-loop-enforcer.js record-result ${SESSION_PATH} <PASS|FAIL> "reason" [score]
  2. If PASS: Proceed to Phase 8

  3. If FAIL: Loop back to Phase 3 (start-iteration will be called again)

OUTER LOOP: Before Phase 8

  1. Verify Phase 7 passed:

    bash
    node ${PLUGIN_PATH}/scripts/outer-loop-enforcer.js check-can-complete ${SESSION_PATH}
  2. 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}
  1. Review generated report: ${SESSION_PATH}/validation/criteria-mapping.md

  2. If unaddressed criteria found:

    • Update result.md to address them
    • Or document why they couldn't be tested

**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"

4. Checkpoint Verifier

Script: scripts/checkpoint-verifier.sh

How it works:

  • Bash script for fast automated checks
  • Runs at phase boundaries
  • Verifies files exist and have content
  • Checks git state for implementation phase

Usage:

bash
# 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 passed

Integration with /dev:feature

Phase Transition Protocol

MANDATORY: Before marking ANY phase as completed:

markdown
<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:

markdown
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.

Show full SKILL.md (249 more words)Show less

Graceful Degradation

Three Completion Statuses

COMPLETE: All validation criteria passed

  • All artifacts created
  • All tests pass
  • Full validation executed

PARTIAL: Some validation done, gaps documented

  • Core functionality verified
  • Some criteria couldn't be tested (documented why)
  • Known limitations listed

INCOMPLETE: Blocked, needs user action

  • Critical blocker encountered
  • Cannot proceed without external input
  • Clear description of what's needed
Session Status in session-meta.json
json
{
  "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": []
}
Final Report for PARTIAL Status
markdown
## 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 roundtrip


5. Failure Report Generator

Script: scripts/failure-report-generator.js

How it works:

  • Auto-generated when phase completion is blocked
  • Documents what was expected vs what happened
  • Lists all attempted approaches and their errors
  • Provides manual testing steps as fallback
  • Includes workarounds and suggestions

When generated:

  • Phase completion validator blocks a phase
  • Validation criteria enforcer finds gaps
  • Outer loop reaches max iterations
  • Any enforcement script fails

Report structure:

markdown
# {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 AskUserQuestion

Usage in orchestrator:

When phase completion is blocked:

markdown
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

Summary Table

EnforcementWhat It Prevents
Phase completion validatorClaiming "done" without proof
Mandatory artifactsSkipping documentation
Validation criteria enforcerCollecting criteria but ignoring them
Outer loop enforcerSkipping retry logic
Phase 6 test checkShipping without tests
Graceful degradationFaking completion when blocked
Show-your-workHiding actual results
Checkpoint verificationAutomated sanity checks
Failure report generatorSilent failures without guidance

Implementation Priority

  1. HIGH: Evidence-based completion + Show-your-work (fixes core trust problem)
  2. HIGH: Validation criteria enforcement (ensures Phase 1 work is used)
  3. MEDIUM: Phase 6 test enforcement (ensures quality)
  4. MEDIUM: Graceful degradation (enables honest status)
  5. LOW: Checkpoint verification (nice automation, but manual review works)

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

Files

Just SKILL.md in plugins/dev/skills/enforcement of MadAppGang/claude-code.

Open the folder on GitHubat commit 6097ad4

Compare with similar skills

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.

Phase Enforcement compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phase Enforcement this skillMadAppGang/claude-code285—~3.4kAutomated safety check: PassMIT
Gsd Phaseopen-gsd/gsd-core10k1 repos~603Automated safety check: NotesMIT
Verification Before Completionforyourhealth111-pixel/Vibe-Skills3.6k—~1.1kAutomated safety check: PassApache-2.0
Verification Before Completionfarm-fe/farm5.6k46 repos~1kAutomated safety check: PassMIT
Bio Phasing Imputation Haplotype PhasingGPTomics/bioSkills1.2k1 repos~4.2kAutomated safety check: PassMIT
Performing Dmarc Policy Enforcement Rolloutmukul975/Anthropic-Cybersecurity-Skills34k—~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Gsd Phase

    open-gsd/gsd-core

    Multi-phase management — add, insert, remove, or edit phases in ROADMAP.md (roadmap phase CRUD)

    10k GitHub starsUsed in 1 repo~603 tokens
    Product & Project ManagementAuto-check: notes
  • Verification Before Completion

    foryourhealth111-pixel/Vibe-Skills

    Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.

    3.6k GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • 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…

    5.6k GitHub starsUsed in 46 repos~1k tokens
    Agent WorkflowsAuto-check passed
  • 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…

    1.2k GitHub starsUsed in 1 repo~4.2k tokens
    Research & ScienceAuto-check passed
  • Performing Dmarc Policy Enforcement Rollout

    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…

    34k GitHub stars~1.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Enforce AIRI's testing and Vitest practices in the AIRI monorepo.

    50k GitHub stars~951 tokensUpdated today
    Testing & QAAuto-check passed

More from MadAppGang/claude-code

All 69 skills in this repo
  • Content Brief

    MadAppGang/claude-code

    Content brief template and creation methodology for SEO-optimized content.

    285 GitHub starsUsed in 1 repo~959 tokens
    Auto-check passed
  • Context Detection

    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…

    285 GitHub stars~5.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Content Optimizer

    MadAppGang/claude-code

    On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.

    285 GitHub starsUsed in 1 repo~694 tokens
    Auto-check passed
  • Keyword Cluster Builder

    MadAppGang/claude-code

    Techniques for expanding seed keywords and clustering by topic and intent.

    285 GitHub starsUsed in 1 repo~674 tokens
    Auto-check passed
  • Serp Analysis

    MadAppGang/claude-code

    SERP analysis techniques for intent classification, feature identification, and competitive intelligence.

    285 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Agent Coordination Discipline

    MadAppGang/claude-code

    A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

    285 GitHub stars~3.8k tokensUpdated 6 mo ago
    Auto-check passed

Questions about Phase Enforcement

What does Phase Enforcement do?

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.

When should I use Phase Enforcement?

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.

How do I install Phase Enforcement in Claude Code?

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.

How do I install Phase Enforcement in Codex?

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.

Can I use Phase Enforcement in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Phase Enforcement need to run?

Going by SKILL.md and its folder, Phase Enforcement needs the command-line tools its instructions call (node).

Does Phase Enforcement access the network?

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.

Is Phase Enforcement safe to install?

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.

What licence does Phase Enforcement use?

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.

How many tokens does Phase Enforcement use?

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.

What are the alternatives to Phase Enforcement?

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.

Who maintains Phase Enforcement?

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.