Files

Paul O'Reilly 884b416d38 Add memory files for review-plan and review-spec skills

Skill documentation for the new plan/spec review skills. Each file
covers purpose, usage, how it works, referenced best practice files,
and gotchas.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-29 11:11:35 +13:00

1.6 KiB

Raw Blame History

Skill: review-spec

Purpose

Reviews a spec file against best practices for structure quality, requirement testability, security coverage, and API design. Ensures specs are implementation-ready before agents start coding.

Usage

/review-spec spec/authentication.md
/review-spec          # reads SPEC.md and prompts to select

How it works

Loads 5 best practice files: spec-driven-development, test-driven-development, api-design, llm-code-security, security-architecture
Reads the specified spec file and SPEC.md index
Evaluates 4 dimensions: structure completeness, requirement quality, security coverage, testability
Checks every numbered requirement for testability, unambiguity, and rationale
Identifies missing requirements and scenarios
Outputs a scored review (1-5 per area), critical issues, missing requirements/scenarios, and recommendations

Best practice files referenced

~/dev/claude/projects/best-practices/spec-driven-development.md
~/dev/claude/projects/best-practices/test-driven-development.md
~/dev/claude/projects/best-practices/api-design.md
~/dev/claude/projects/best-practices/llm-code-security.md
~/dev/claude/projects/best-practices/security-architecture.md
Plus any tech-stack-specific files from the index

Gotchas

Read-only skill (allowed-tools: Read, Glob, Grep, Bash cat/ls/find). Cannot edit files.
Relies on best-practices repo being cloned at ~/dev/claude/projects/best-practices/
The ~/ path in the bang-command generates a validator warning but works in practice
Counts requirements and verifies summary counts -- catches stale counts after edits

1.6 KiB Raw Blame History