Pharn Dev Build — Testing skill for Claude Code
Execute ONE approved PLAN.md increment.
How to install Pharn Dev Build
Installs to ~/.claude/commands/pharn-dev-pharn-oss-pharn-dev-build.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/pharn-dev/pharn-oss/HEAD/.claude/commands/pharn-dev-build.md -o ~/.claude/commands/pharn-dev-pharn-oss-pharn-dev-build.md Restart Claude Code, or start a new session, for it to be picked up.
What Pharn Dev Build does
description: "Execute ONE approved PLAN.md increment. Verify the spec content-hash still matches, write each Capability WITH its evals, run the deterministic floor, halt on any RED. Never builds an unapproved or drifted plan." role: skill kind: pharn-owned trust: trusted model_tier: sonnet model: sonnet effort: high reads: ["pharn/CONSTITUTION.md", "pharn/ARCHITECTURE.md", ".dev/features//PLAN.md", ""] writes: [""] constitution_refs: ["P0", "P1
Alternatives in Testing
- Testing Strategy — This project is small, runs in a terminal, and is mostly deterministic 10.9k ★
- Next Evals OSS — Evals for Next.js up to 15.5.6 to test AI model competency at Next.js 310 ★
- Superpowers Evals — Behavioral eval lab (Quorum) for the superpowers project that drives real coding-agent CLIs (Claude, Codex, Ge 107 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Pharn Grill
Interrogate an approved features/ /PLAN.md AND deterministically re-verify TWO things — the spec→plan hash cha
Pharn Dev Verify
Verify the feature was built CORRECTLY through two cleanly-separated layers. FLOOR layer: re-run the existing
Spec To Tickets
Break a capability spec (or the shaping conversation that produced it, or a parent issue) into tracer-bullet t
Ihudak Claude Plugins
Claude Code plugins for the full feature lifecycle: idea → Value Increment → ARD → spec → design → Epics → imp
Halt Check
Smoke test — verify every hook and middleware respects the HALT kill switch. Advisory, read-only.
Continuous Retest Loop
Re-test a target on every change instead of once per engagement — detect drift, then re-run ONLY the affected
Related Agents
Gsd Dom Verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VE
Harness AI Dev
AI engineer — LLM and agent features, prompts, model integration, tool definitions, retrieval, and the evals t
Doc Impact Verifier Light
Verifies whether a single documentation file still matches a described source-code/config change. Report-only;