collaboration-impact-receipt

Name: collaboration-impact-receipt
Availability: InStock
Author: aurora-atoms

Generate evidence-backed impact receipts for collaborative delivery contributions.

Updated Jun 1, 2026

Search Tags:#collaboration #governance #evidence #attribution #delivery #impact

Ready to run

npx skills add https://github.com/aurora-atoms/lattice --skill collaboration-impact-receipt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: collaboration-impact-receipt
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/collaboration-impact-receipt
Command: npx skills add https://github.com/aurora-atoms/lattice --skill collaboration-impact-receipt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of recognizing meaningful teamwork without resorting to superficial activity metrics or surveillance-based performance scoring.

Core Features & Use Cases

Outcome-Linked Recognition: Connects specific contributions to tangible delivery changes like unblocking work or resolving risks.
Collaborative Verification: Facilitates participant confirmation and attribution management to ensure factual accuracy and shared credit.
Use Case: Use this after a cross-team effort where your intervention resolved a critical dependency, ensuring the impact is documented with evidence and participant agreement rather than just commit counts.

Quick Start

Use the collaboration-impact-receipt skill to generate a verified impact record for the recent database migration blocker resolution by linking the relevant feature delivery case and participant evidence.

Frequently Asked Questions about collaboration-impact-receipt

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

FAQPage Schema

How do I document cross-team dependency resolution with evidence-based attribution?▼

You document cross-team dependency resolution by generating an impact receipt that links participant evidence to specific delivery outcomes. This requires explicit participant confirmation to ensure factual accuracy and shared credit without surveillance metrics.

What is the best way to recognize collaborative contributions without relying on superficial activity metrics?▼

The best way to recognize collaborative contributions is outcome-linked recognition, which connects specific interventions to tangible delivery changes like unblocking work or preventing risks. This approach avoids superficial activity metrics by requiring evidence-backed attribution.

When do I need to generate an impact receipt for feature delivery cases?▼

You need to generate an impact receipt when a collaborative contribution materially changes a delivery outcome, such as an unblocking event or risk prevention within a feature delivery case. It operates within this scope to document cross-team dependencies accurately.

How do I ensure factual accuracy for collaborative verification of delivery impact?▼

You ensure factual accuracy for delivery impact by facilitating participant confirmation and attribution management. This collaborative verification enforces human authority, requiring explicit agreement from participants before documenting the shared credit.

Can I use collaboration-impact-receipt for tracking unblocking events across cross-team efforts?▼

Yes, you can use it for tracking unblocking events across cross-team efforts. It operates within the scope of feature delivery cases to document these unblocking events, ensuring any intervention that resolved a critical dependency is recorded with participant agreement.

Does evidence-backed visibility for delivery impact require explicit participant confirmation?▼

Yes, evidence-backed visibility for delivery impact requires explicit participant confirmation. This ensures that the attribution of collaborative contributions to delivery outcomes remains factually accurate and maintains human authority over the shared credit.