pbs-spec-driven

Plans and implements features through adaptive spec-driven phases with deterministic validation gates.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Peterson-Benhame/agent-skills --skill pbs-spec-driven-peterson-benhame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pbs-spec-driven
Source: https://github.com/Peterson-Benhame/agent-skills/tree/main/packages/skills-catalog/skills/%28development%29/pbs-spec-driven
Command: npx skills add https://github.com/Peterson-Benhame/agent-skills --skill pbs-spec-driven-peterson-benhame

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Feature work with AI agents often drifts: vague requirements, skipped tests, batched commits, and self-verified code that passes review but fails in production. This Skill enforces a disciplined Specify → Design → Tasks → Execute workflow where requirements are testable, commits are atomic, and an independent Verifier (author ≠ verifier) validates the result with evidence before anything is called done. ## Core Features & Use Cases - Adaptive 4-phase workflow: Auto-sizes depth by complexity (Small/Medium/Large/Complex), writing EARS-notation requirements, atomic tasks, and Conventional Commits only as deep as the feature needs. - Deterministic validation scripts: Python gates (validate_spec.py, validate_tasks.py, check_commit.py, validate_state.py) enforce structural rules by code, not by model memory. - Independent Verifier with discrimination sensor: A fresh sub-agent re-derives test coverage from the spec, injects behavior-level mutations to confirm tests actually catch regressions, and writes an evidence-based validation report. - Project memory and lessons layer: STATE.md decision log and handoff snapshots enable pause/resume, while lessons.py distills verification failures into reusable project-local guidance. - Use Case: Ask the agent to "specify feature: user notification preferences" — it produces a testable spec, breaks it into atomic tasks, implements each with its own commit, then runs an independent verification pass before declaring completion. ## Quick Start Ask the agent to specify and implement a new feature, for example: "specify feature: add password reset flow, then implement it with verification."

Frequently Asked Questions about pbs-spec-driven

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and implement a feature with spec-driven development?

Trigger the workflow with phrases like "specify feature" or "implement". The skill auto-sizes depth by complexity: small changes get an inline spec, while large features get full EARS requirements, design docs, atomic tasks, and per-task commits with verification.

What are EARS notation requirements in a spec?

EARS (Easy Approach to Requirements Syntax) structures acceptance criteria into testable patterns like "when X, the system shall Y". The validate_spec.py script enforces EARS-shaped acceptance criteria, filled assumptions, and well-formed requirement IDs before a spec is approved.

Does this skill work with any programming language or framework?

Yes, it is stack-agnostic and tool-agnostic. The workflow operates on Markdown artifacts in a .specs/ directory and uses pure standard-library Python scripts, so it works with any codebase, test runner, or AI coding agent.

How does the independent Verifier validate completed work?

After the last task commits, a fresh Verifier sub-agent re-derives test coverage from the spec using evidence-or-zero rules, injects behavior-level mutations in a scratch copy to confirm tests catch regressions, and writes a PASS/FAIL validation report with file:line evidence.

When should I not use spec-driven development?

Do not use it for pure architecture decomposition analysis or standalone technical design documents. It is designed for feature planning, implementation with verification, and validating implementations against a spec.

How do I pause and resume feature work across sessions?

Say "pause work" to write a handoff snapshot to .specs/STATE.md, then "resume work" later. The agent reconciles the snapshot against git state and tasks.md, since evidence wins over a stale snapshot, then proposes the next step.