handoff-spec

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

• 0

  Common

  Most of the 7 edited versions we read keep these.

• 1

  Distinctive

  This author's own choices. Worth a look.

• 0

  Very specific

  Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

• Other versions10 projects use a version of this.

  Word for word · 1

  1. miovrag/claude-skills★ 1100% same

  Edited · 0

  None found.

  Wrote their own version · 9

  1. dzhng/jevgrep★ 3.1ksame name
  2. dzhng/skills★ 1.4ksame name
  3. dzhng/yap★ 112same name
  4. dzhng/duet-agent★ 55same name
  5. sidneyswift/skills★ 9same name
  6. Buddhilive/buddhi-cli★ 1same name
  7. cskwork/handoff-spec-kit★ 1same name
  8. aiuxmasters/agentic-design-tools★ 0same name
  9. tjrice42/design-judgment-skills★ 0same name

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• Used alongsideProjects with it also use close-spec, design-with-images and 9 more.

  Other files people use alongside this one.

  How we pick theseFiles found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 4 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 4 projects that use this

  • transitive-bullshitSkill

    compare-screenshots

    Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

    Also in 4 projects that use this

  • LucasMatuszewskiSkill

    audit-agents

    Audit and maintain agent configuration files (.claude/agents, AGENTS.md, CLAUDE.md, agent-memory). Checks for duplicates, outdated info, naming conflicts, wrong technical facts, and files over 200 lines. Fixes all issues and commits.

    Also in 4 projects that use this

  • rhnfzlSkill

    explore-unknowns

    Walk the user through mapping the unknowns of a task before, during, and after they build it, and hand them a four-quadrant map (settled ground, open decisions, taste, and landmines) they keep. Reach for this eagerly whenever a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, a build-queue or architecture-changing task is about to start, a mid-build deviation needs capturing, or a finished change needs buy-in or verified understanding before merge. Trigger even when the skill is not named: "do a blindspot pass", "find my unknown unknowns", "interview me about this change", "brainstorm the approach for a task I am about to build", "help me scope this", "what am I missing here", "plan this before I build", "I know nothing about X in this codebase". When a territory profile is present it reads memory and the graph first and feeds the map into the build pipeline; without one it degrades to a plain general map. Not for trivial or mechanical tasks with clear acceptance criteria, single-fact lookups, pure debugging of a known symptom, or pure code review, those have their own tools. Do not use it to run the build itself; the map is the deliverable and implementation remains a separate task, whether it has not started or is already underway.

    Also in 4 projects that use this

  • isLinXuSkill

    eval-skills

    AI Agent Skill unit testing framework. A framework-agnostic toolkit for discovering, scaffolding, selecting, evaluating, and reporting on AI skills. Use this skill to assess skill quality before production, compare candidate skills on the same benchmark, enforce quality gates in CI/CD, and generate human-readable evaluation reports.

    Also in 4 projects that use this

  • +4 more from dzhng
• In this repository73 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • rust-skillsAGENTS.md
  • rust-skillsCLAUDE.md
  • CLAUDE.mdCLAUDE.md
  • code-review-excellenceSkill
  • rust-architectSkill
  • rust-skillsSkill
  • a-b-test-designSkill
  • accessibility-auditSkill
  • accessibility-test-planSkill
  • affinity-diagramSkill
  • animation-principlesSkill
  • card-sort-analysisSkill
  • case-studySkill
  • click-test-planSkill
  • code-review-excellenceSkill
  • color-systemSkill
  • competitive-analysisSkill
  • component-specSkill
  • dark-mode-designSkill
  • data-visualizationSkill
  • design-briefSkill
  • design-critiqueSkill
  • design-principlesSkill
  • design-qa-checklistSkill
  • design-rationaleSkill
  • design-review-processSkill
  • design-sprint-planSkill
  • design-system-adoptionSkill
  • design-token-auditSkill
  • design-tokenSkill
  • diary-study-planSkill
  • documentation-templateSkill
  • empathy-mapSkill
  • error-handling-uxSkill
  • experience-mapSkill
  • feedback-patternsSkill
  • gesture-patternsSkill
  • heuristic-evaluationSkill
  • icon-systemSkill
  • illustration-styleSkill
  • interface-designSkill
  • interview-scriptSkill
  • jobs-to-be-doneSkill
  • journey-mapSkill
  • layout-gridSkill
  • loading-statesSkill
  • metrics-definitionSkill
  • micro-interaction-specSkill
  • naming-conventionSkill
  • north-star-visionSkill
  • opportunity-frameworkSkill
  • pattern-librarySkill
  • presentation-deckSkill
  • prototype-strategySkill
  • responsive-designSkill
  • rustdocSkill
  • spacing-systemSkill
  • stakeholder-alignmentSkill
  • state-machineSkill
  • The first 60 shown.