spec-trace

Generate and validate AI session execution traces from implementation metadata.

Updated Jul 7, 2026

Search Tags:#workflow #documentation #audit #metadata #trace #spec-kit

Ready to run

npx skills add https://github.com/eavichay/mycli --skill spec-trace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-trace
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/spec-trace
Command: npx skills add https://github.com/eavichay/mycli --skill spec-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of documenting complex AI-driven development sessions by automatically synthesizing implementation metadata into a structured, human-readable narrative.

Core Features & Use Cases

Narrative Synthesis: Automatically generates a Problem-Decision-Solution summary from feature artifacts.
Technical Auditing: Captures quality gate statistics, decision patterns, and evidence links for future reference.
Use Case: After completing a complex feature implementation, use this skill to generate a trace file that serves as a permanent record for knowledge transfer and future code reviews.

Quick Start

Run the spec-trace skill to generate a comprehensive execution trace for the current feature branch.

Frequently Asked Questions about spec-trace

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

FAQPage Schema

How do I generate an execution trace for AI-driven development sessions?▼

To generate an execution trace, use a tool that synthesizes implementation metadata into a structured Problem-Decision-Solution narrative, capturing decision patterns and quality gate results for your feature branch.

What is a feature execution trace in software development workflows?▼

A feature execution trace is a human-readable record documenting AI session decisions, technical evidence, and quality gate statistics, serving as a permanent artifact for knowledge transfer and code reviews.

Does generating feature execution traces require a specific project structure?▼

Generating execution traces requires a spec-kit project structure containing a .specify directory and existing task metadata to correctly synthesize implementation artifacts and validate quality gates.

How do I document decision-making patterns and technical evidence after feature implementation?▼

You can document decision-making patterns by automatically synthesizing implementation metadata into a structured trace file that captures quality gate statistics, technical evidence links, and narrative summaries.

When should I avoid using automated trace generation for software documentation?▼

You should avoid automated trace generation if your project lacks the required spec-kit structure, a .specify directory, or existing task metadata, as these elements are mandatory for synthesizing valid execution traces.