handoff-test

Audits session artifacts for implicit dependencies and gaps.

12|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/hartphoenix/weft --skill handoff-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-test
Source: https://github.com/hartphoenix/weft/tree/main/.claude/skills/handoff-test
Command: npx skills add https://github.com/hartphoenix/weft --skill handoff-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill detects implicit dependencies and gaps within session artifacts to ensure clarity and completeness before context compaction or session end. It helps prevent misunderstandings by auditing and identifying overlooked assumptions.

Core Features & Use Cases

  • Artifact auditing: Reads session-created or modified artifacts to identify ungrounded references and missing information.
  • Gap reporting: Finds implicit dependencies like undefined terminology, unstated rationale, or broken links.
  • Use Case: Before finalizing session notes, use this Skill to ensure all references are grounded and decisions are rationalized.

Quick Start

Drop this Skill into your session directory and run the review process to validate your session artifacts for implicit dependencies.

Frequently Asked Questions about handoff-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What does an implicit dependency audit do for session artifacts?

An implicit dependency audit identifies ungrounded references and missing information within session artifacts to prevent miscommunication before context loss or compaction.

How do I audit session notes for missing rationale before finalizing?

Run a review process on your session directory to scan artifacts for implicit dependencies, ensuring all references and decisions are rationalized before finalizing session notes.

Do I need external libraries to audit session artifacts for gaps?

No external libraries are required to audit session artifacts for gaps; the process operates within your existing environment to identify unstated rationale and broken links.

When should I review artifacts for implicit dependencies?

You should review artifacts for implicit dependencies before context compaction or session end to ensure clarity and prevent overlooked assumptions in conversation summaries.

What is the best way to find undefined terminology in conversation summaries?

The best way to find undefined terminology is to perform a gap reporting review on session artifacts, which detects implicit dependencies and missing information.