Claude Skills by GiustoPiedimonte

This skill should be used to record an architecture decision. Trigger when the user says "record this decision", "write an ADR", "we decided to...", "log why we chose X", or when a consequential, hard-to-reverse technical choice is made. Appends a dated, immutable decision block to the decision log.

This skill should be used to make eval the unit of progress: systematize how a feature or agent is judged. Trigger with "how do we eval this", "build an eval harness", "why is the agent failing", "error analysis", "are we regressing", or before flipping an eval-gated dark launch. Builds evals from REAL failures (not synthetic), localizes where a pipeline breaks, and feeds flip-criteria.

This skill should be used to design or run a task as a graph instead of a linear chain — fan out independent work across a fleet of subagents, verify findings, and converge. Trigger with "run this as a graph", "fan this out", "parallelize this", "orchestrate this with subagents", "audit every X", "sweep the codebase for Y", or any breadth job one context can't hold. Turns a straight-line agent into an execution graph (diamond / router / verifier / cycle) built on dynamic workflows.

This skill should be used to unblock a decision that needs data. Trigger with "measure this", "do users actually...", "check the numbers before we cut/keep", "did the change land". Runs a read-only measurement and returns a data-backed flip/keep/cut verdict — never guesses, never writes.

This skill should be used to shape a feature into a written spec before any code. Trigger when the user says "shape this", "write a pitch", "spec this out", "let's plan <feature>", or starts non-trivial work without an agreed approach. Produces a Shape Up style pitch (the source of truth) via interview.

Execute an approved pitch/spec as a delegated, closed-scope cycle with verification and adversarial review. Invoke it yourself with /ship <pitch> — a cycle spawns a writer and opens a PR, so it starts when you say so. Enforces the execution playbook: right-size gate, pre-spawn filter, doc-bundle, PR format, review.

This skill should be used to make a repository a well-made public/open-source project. Trigger with "make this repo public-ready", "set up open source", "add a code of conduct / contributing / security policy", "add issue and PR templates", "add CI", "fix the repo settings", or "get this ready to share". Adds the community-health files, an honest CI gate, and the right repo settings — honesty-first, and never flips a repo public or changes settings without explicit confirmation.

This skill should be used to audit OR elevate the README of a public repository. Trigger with "improve the README", "make the readme high quality", "elevate this readme", "audit the readme", "add badges", "is our README good", or before publishing/releasing a repo. Elevate rebuilds a thin/generic README to a polished, repo-specific one (banner, honest live badges, custom chips, cognitive-funnel structure) — every signal derived from the actual repo. Honesty-first: never adds a signal the repo...