trace

Trace design decisions across sessions, handoffs, and git into a markdown report.

418|40|Updated Nov 5, 2025

Search Tags:#git #timeline #provenance #trace #session history #handoffs #design decisions

Ready to run

npx skills add https://github.com/boshu2/agentops --skill trace-boshu2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/boshu2/agentops/tree/main/skills/trace
Command: npx skills add https://github.com/boshu2/agentops --skill trace-boshu2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires provenance.

What problem does it solve?

Trace design decisions and provenance across session history, handoffs, and git to build a verifiable decision history.

Core Features & Use Cases

Timeline construction: aggregate decisions from sessions, handoffs, and commits into a single chronology.
Provenance extraction: capture rationale, authors, and evidence to trace why design choices were made.
Cross-source correlation: align transcripts, handoffs, and repository history to reveal how concepts evolved.

Quick Start

Use the trace skill to surface the decision history for a concept or artifact. The skill will search sessions, handoffs, and git history and output a markdown trace to .agents/research/YYYY-MM-DD-trace-<concept-slug>.md

Frequently Asked Questions about trace

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

FAQPage Schema

How do I track design decisions across git history and session handoffs?▼

Design decision provenance is captured by extracting rationale, authors, and evidence from session transcripts, handoffs, and git history. This traces exactly why specific software architecture or product choices were made across multiple sources.

What is the best way to build a verifiable timeline of rationale for research artifacts?▼

The best way to build a verifiable timeline of rationale is to correlate cross-source evidence from transcripts, handoffs, and repository history. This aggregates design decisions into a single chronology, revealing how research artifacts evolved over time.

Does tracing session history and provenance require capturing transcripts and commit messages?▼

Yes, tracing session history and provenance requires capturing transcripts, handoffs, commit messages, and artifacts as input. These sources are then aligned to extract rationale and assemble the final trace report.

How do I generate a markdown trace report for software architecture choices?▼

You generate a markdown trace report for software architecture choices by searching session and git history for a specific concept. The output is saved directly to .agents/research/YYYY-MM-DD-trace-<concept-slug>.md.

Do I need the provenance dependency to extract design decision history?▼

Yes, you need the provenance dependency to extract design decision history. It provides the foundational mechanism for capturing and verifying the rationale, authors, and evidence from your session history and git commits.