Claude Skills by armanfatemi

Get review or advice on your work from this repo's four reviewer agents in `.claude/agents/`. The protocol is: list every candidate whose domain overlaps the change, write a one-line SPECIFIC justification of why each applies to THIS change, drop any whose justification is generic or duplicated by a narrower candidate, and dispatch only the survivors in parallel with focused, well-briefed requests. Use whenever the user says "get advice", "ask the experts", "review with the agents", "what do ...

Transform a raw idea into one or more well-defined OpenSpec proposals through guided dialogue, codebase survey, feasibility review, and decomposition. Use when the user has an idea they want to develop into a proposal — or when given a problem to solve, and its shape is not yet decided. The output is a complete, implementation-ready change directory with enriched proposal.md, design.md skeleton, and tasks.md skeleton.

Drive an OpenSpec change from proposal to merge-ready PR. Reads `openspec/changes/<name>/`, blocks at Stage 1 until every prerequisite named in the proposal's `> **Depends on:**` blockquote has reached `main`, plants a canary and runs parallel reviews on the proposal, refines until zero blockers, implements each task, verifies with an auto-fix loop that knows the ugrep baseline, re-reviews the diff, and opens a PR seeded with review evidence. Never merges. Resumable — state persists in `.git/...

Ground documents in verifiable citations. Use whenever writing or editing ANY document a human will approve or review that asserts something about the EXISTING codebase — a design doc, proposal, RFC, ADR, risk assessment, a PLAN (including plan mode), or a PR DESCRIPTION. Load-bearing claims must carry Evidence Anchors that the deterministic checker (npx @nullius-inverba/claims) can re-verify; a claim you cannot cite goes to "Open questions" instead.