implement-spec
This skill runs locally or in Claude Code cloud (claude.ai/code) — NOT in CI. It needs write access to the repo to create commits and push to the PR branch.
<Execution_Policy>
- The spec is the source of truth. Implement what it says, not more.
- Read CLAUDE.md for project conventions, testing requirements, and architecture.
- Each phase must complete before the next begins.
- Parallel execution within phases where possible.
- QA cycles repeat up to 5 times; if the same error persists 3 times, stop and report.
- If something in the spec is ambiguous, post a PR comment rather than guessing.
- Do not add features, refactor code, or make improvements beyond the spec. </Execution_Policy>
Phase 1: Plan
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
3new-spec
Create a new spec through Socratic interview, filling each template section to zero ambiguity
2analyze-spec
Spec analysis with ambiguity scoring — interactive locally, single-pass remotely via label
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