Create, revise, and audit technical specifications following RFC/IETF conventions. Use when the user wants to write a new spec, edit an existing spec, review a spec for completeness, or formalize a design decision into a specification document. Triggers on "write a spec", "spec for", "formalize this", "draft a specification", "audit this spec", "revise the spec", "protocol spec", "format spec", or any request to create structured technical documentation with normative requirements. Also triggers when the user has a brainstorm decision record they want to turn into a formal spec.
From provenpx claudepluginhub mjmorales/claude-prove --plugin proveThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
Orchestrate spec lifecycle (create, revise, audit). Delegate all writing to the spec-writer agent.
If not obvious from context, use AskUserQuestion (header "Mode") with "Research & proceed" per references/interaction-patterns.md:
specs/)Default to Revise if $ARGUMENTS points to a .spec.md file. Default to New Draft if it references a .prove/decisions/ record.
New Draft:
specs/ for related specs to cross-referenceRevise:
Audit:
Launch with a structured prompt. The agent handles RFC conventions, section structure, terminology, and self-auditing.
New Draft:
Mode: New Draft
Subject: [title]
Version: 0.1 (Draft)
Input context: [decision records, brainstorm notes, or requirements]
Scope:
- In scope: [what the spec defines]
- Out of scope: [what it excludes]
Related specs: [existing specs in specs/ to cross-reference]
Write to: specs/[slug].spec.md
Revise:
Mode: Revise
Spec path: specs/[name].spec.md
Current version: [X.Y]
Changes requested: [what to add, remove, or modify]
Version bump: [major | minor]
Update in place.
Audit:
Mode: Audit
Spec path: specs/[name].spec.md
Run the full Completeness Checklist. Report findings as:
- Location (section number or line)
- Issue description
- Severity (Critical / Important / Improvement)
- Suggested fix
Do not modify the spec.
New Draft: Verify file at specs/[slug].spec.md follows expected structure (Purpose, Scope, Terminology, Conformance, normative body, Change Log). Report location and version.
Revise: Verify version bump, Change Log update, and cross-reference resolution. Report changes.
Audit: Present findings by severity. Use AskUserQuestion (header "Next step"): "Fix issues" (switch to Revise) / "Done".
Delegate to the commit skill. Examples:
docs(spec-writer): draft validation config v2 specificationdocs(spec-writer): revise handoff protocol — add context fieldsspec-writer agent; this skill orchestrates only.