Cherridsaid

Phases Agents — Development skill for Claude Code

Development community

Local MCP server for deterministic skill selection.

How to install Phases Agents

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Cherridsaid/phases-agents and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Phases Agents does

Local MCP server for deterministic skill selection. Discovers, validates and plans. Zero dependencies, nothing executed.

Alternatives in Development

Ccusage — CLI for analyzing Claude Code/Codex usage from local JSONL files 11.8k ★
Implement Plan — You are tasked with implementing an approved technical plan from thoughts/shared/plans/ 10k ★
Sanitize — Detect and redact PII from text files — 15 categories (SSNs, credit cards, API keys, etc.), zero dependencies 3.1k ★

README

phases-agents

*English · [Français](README.fr.md)*

![phases-agents: select, block, prove](https://raw.githubusercontent.com/Cherridsaid/phases-agents/main/docs/banner.png)

A local MCP server that discovers, validates and selects skills deterministically. Python standard library only, no runtime dependencies.

One server. Five tools. Nothing executed behind your back.

Why

AI agents improvise. Ask the same question twice and you get two different plans. That is fine for brainstorming, and unacceptable for audit and compliance work.

phases-agents removes the improvisation. It profiles a local project, validates a catalogue of skills against a strict contract, and returns a plan that can be replayed. Same target, same catalogue, same parameters, same decision.

Principle

![Same inputs, same plan](https://raw.githubusercontent.com/Cherridsaid/phases-agents/main/docs/determinism.png)

configured root identifiers
→ bounded discovery
→ official validation
→ immutable registry
→ verified cache
→ detector profile
→ deterministic selection
→ MCP plan

The server selects and exposes. The calling model reads the selected skills and decides what to do with them, using its own tools. **The server never executes a skill.**

Architecture

The modules live in `src/phases_agents/`.

File	Role
`validator.py`	official contracts and validated snapshots
`skill_loader.py`	bounded local discovery
`skill_runtime.py`	trusted roots and verified cache
`skill_types.py`	immutable types and limits
`registry.py`	validated, immutable registry
`detector.py`	local profile of the target
`planner.py`	deterministic selection and ordering
`server.py`	JSON-RPC/MCP transport
`capabilities.py`	client capability vocabulary
`profile_facts.py`	versioned profile-fact vocabulary
`skill_gaps.py`	gap rules (`skills_missing`)