All authors
Claude Skills by rioffe
github.com/rioffe7 skills0 installs3 views
- Spec BuildImplement a SPEC.md in any language or stack via test-driven development **executed wave by wave against an implementation plan this skill produces first**, then make README.md reflect the built reality, re-read SPEC.md, audit every produced artifact for conformance, and run and **look at** the product against the spec's reference images (or report VERIFICATION PENDING), writing SPEC_BUILD_REPORT.md. Phase 0 runs spec-plan to write IMPLEMENTATION_PLAN.md and one DETAILED_IMPLEMENTATION_PLAN_W...Votes: 0GitHub stars: 3
- Spec ModelBuild the formal (Lean 4) model of a SPEC.md when no implementation exists yet — a lake project in `proof_from_spec/` (`lean-toolchain`, `lakefile.toml`, `lake-manifest.json`, `README.md`) that transcribes the spec's normative tables into a pure total Lean function, kernel-checks the spec's *derived* claims for all inputs (exit/status map, byte contracts, diagnostics, invariants, reachability, coverage — that the input space has no silent case), and reifies every under-specified, over-pinned,...Votes: 0GitHub stars: 3
- Spec PlanTurn a SPEC.md (plus its SPEC_REVIEW_REPORT.md when one exists) into an IMPLEMENTATION_PLAN.md — the verdict, the evidence from any prior builds, the target shape, the dependency-wave order with a gate per wave, the LOC budget, the structural rules that make the observed failures impossible, and the single fork decision — and, when the waves are big enough to execute one at a time, into per-wave DETAILED_IMPLEMENTATION_PLAN_WN.md documents. Use when asked to "plan the implementation", "make a...Votes: 0GitHub stars: 3
- Spec ProofCreate the formal (Lean 4) half of the conformance evidence for a built system — a self-contained lake project in the project's `proof/` directory (`lean-toolchain`, `lakefile.toml`, `lake-manifest.json`, `README.md`) that transcribes the spec's deterministically-provable contract into a Lean model and proves it kernel-checked for all inputs, while mapping every unprovable row to the empirical test that carries it. Phases are read the spec and classify every ID as proven / structural / deferr...Votes: 0GitHub stars: 3
- Spec ProposalWrite a PROPOSAL document — a scoped, evidence-grounded change to an existing, already-implemented SPEC.md or tool, not a greenfield spec. Encodes the fixed six-section template (problem, change, cost, alternatives, decisions for the requester, what it doesn't fix) with its front-matter blockquote, draft R/C/I/K/E/T rows for spec-writing to fold in once confirmed, and the two-column decision table (ID | Statement, each cell an option-versus-option choice with a recommendation). Use for "write...Votes: 0GitHub stars: 3
- Spec ReviewReview a software specification treated as SPEC.md (the source of truth for the system under review) for completeness, internal consistency, semantic precision, implementability, and verifiability. Use it when auditing or grading a spec before implementation, or when asked how precisely it constrains both an implementer and a verifier. Applies a domain-agnostic four-pass method (comprehension, local precision, cross-consistency, implementation simulation) across 20 review dimensions (requirem...Votes: 0GitHub stars: 3
- Spec WritingAuthor a Level-3 (implementation-grade) SPEC.md for any software system, in any language, stack, or domain. Use when asked to "write a spec", "create SPEC.md", "specify this system/interface/pipeline", or turn requirements, a design doc, or a conversation into a spec an agent can implement and verify. Encodes the 13-section template (intent, actors, requirements, behavior/state, contracts, interfaces, invariants, constraints, edge cases, tests, dependencies, traceability, open questions and d...Votes: 0GitHub stars: 3