Spec Checklist — Testing skill for Claude Code
Helper — Generates a customized acceptance-criteria checklist for the current feature, based on spec.md and design.md.
How to install Spec Checklist
Installs to ~/.claude/skills/plocemourasouza-osforge-spec-checklist/SKILL.md
mkdir -p ~/.claude/skills/plocemourasouza-osforge-spec-checklist && curl -fsSL https://raw.githubusercontent.com/plocemourasouza/osforge/HEAD/commands/spec-checklist.md -o ~/.claude/skills/plocemourasouza-osforge-spec-checklist/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
What Spec Checklist does
description: Helper — Generates a customized acceptance-criteria checklist for the current feature, based on spec.md and design.md. Use before considering the implementation complete or to generate QA criteria. Triggers: "checklist", "acceptance criteria", "QA checklist", "ready to test", "/spec-checklist [feature]".
Required context
Read before executing:
.specs/features/[feature]/spec.md— source of the Acceptance Criteria.specs/features/[feature]/design.md— contracts and
Alternatives in Testing
- Claude Code Spec Workflow — Automated Kiro-style Spec workflow for Claude Code 3.6k ★
- Contributing To Playwright Skill — Thank you for considering contributing to the Playwright Skill plugin for Claude Code 2.1k ★
- Spec Driven Development — Drive Kandev feature work through spec, plan, independent tasks, implementation, QA, and verification 697 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Cfn Spec
SPARC Specification phase. Make testable acceptance criteria, edge cases, pre/post conditions, invariants BEFO
Spec
Define what to build — explores codebase and recalls LTM before writing acceptance criteria.
Unity Refine
Refines a raw GitHub issue into an implementation-ready spec — problem, acceptance criteria, scope, affected s
Spec Writer
Specification writer that turns vague intent into precise, buildable specs with acceptance criteria and GitHub
Amby.Specify
Turn a feature idea into a spec — user stories, EARS requirements, acceptance criteria.
Spec Specify
Phase 1 — Creates the detailed technical specification of a feature: functional requirements, non-functional r
Related Agents
Feature Crew Tester
Writes tests against spec.md acceptance criteria (NOT against implementation). Invoked after Build. Reads spec
Spec Verifier
Spec compliance verifier - independently checks the implementation against the plan's acceptance criteria and
Plan Execution Checker
Validates completed plan implementation by verifying all requirements met, code quality standards followed, an