analyze-spec
This skill operates in two modes:
- Local mode (invoked via
/analyze-specin Claude Code): Full interactive Socratic interview — one question at a time, iterative refinement with the spec author. - Remote mode (triggered externally via the
claude-spec-review-requestlabel): Single-pass analysis — all questions posted at once as a single PR comment. Reads prior PR comments as context to account for already-answered questions.
Adapted from the Ouroboros-inspired deep interview methodology — specification quality is the primary bottleneck in AI-assisted development.
<Execution_Policy>
- Gather codebase facts via
exploreagent BEFORE asking about them - Cite repo evidence (file path, symbol, or pattern) instead of asking the spec author to rediscover it
- Score ambiguity transparently
- Do not approve until ambiguity ≤ threshold (default 0.2)
- Allow early approval with a clear warning if ambiguity is still high </Execution_Policy>
<Mode_Detection>
More from a16z/jolt
jolt
Wrap a Rust function in a Jolt zero-knowledge proof
15new-objective
Implement a new objective for jolt-eval
3new-invariant
Implement a new invariant for jolt-eval
3implement-spec
Autonomous one-shot implementation from an approved spec (local/cloud only)
3new-spec
Create a new spec through Socratic interview, filling each template section to zero ambiguity
2ci-code-review
Deep code review of a pull request using parallel analysis agents (semantic consistency, bugs, tech debt, security). USE FOR: - Reviewing PRs for bugs, security issues, and code quality - Analyzing new abstractions for consistency and correctness - Identifying tech debt and architectural concerns - Posting review comments to specific lines on GitHub TRIGGERS: - "review PR", "code review", "review changes" - "diff review", "PR feedback", "check PR" - "analyze diff", "critique code", "review code" - "pull request review", "GitHub PR review"
2