aidlc-superpowers-tracking

Analyze audit logs and state files to summarize skill usage and failures.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-superpowers-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-superpowers-tracking
Source: https://github.com/bluejayA/devflow-aidlc-like/tree/main/skills/aidlc-superpowers-tracking
Command: npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-superpowers-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify inefficiencies and opportunities for improvement in your AI-driven development workflows by analyzing how skills and patterns are used.

Core Features & Use Cases

  • Session Summary: Parses audit logs to list invoked skills, their status (completed, skipped, failed), and user gate choices.
  • Pattern Analysis: Compares data across multiple sessions to find frequently skipped or failed steps, indicating potential workflow issues or skill deficiencies.
  • Tuning Suggestions: Provides actionable recommendations for workflow optimization based on usage patterns, such as suggesting prompt improvements for frequently failing skills or reviewing minimal depth settings for skipped stages.

Quick Start

Run the aidlc-superpowers-tracking skill to analyze the current session's skill usage.

Frequently Asked Questions about aidlc-superpowers-tracking

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

FAQPage Schema
How do I analyze audit logs to optimize my AI-driven development workflow?

Analyzing audit logs optimizes AI-driven development workflows by parsing session state files to summarize invoked skills, identify failure points, and suggest actionable tuning improvements. It reviews completed, skipped, and failed steps to find workflow inefficiencies.

What is the best way to find frequently skipped or failed steps in my development session?

Finding frequently skipped or failed steps requires pattern analysis across multiple development sessions to identify recurring workflow issues or skill deficiencies. It compares historical audit logs to detect these common failure points and highlight areas needing prompt improvements.

Can I get tuning suggestions for workflow optimization based on usage patterns?

You can get tuning suggestions for workflow optimization by analyzing usage patterns from your session audit logs. It provides actionable recommendations such as prompt improvements for frequently failing skills or reviewing minimal depth settings for skipped stages.

What files do I need to parse for comprehensive session skill tracking?

Comprehensive session skill tracking requires parsing devflow-audit.md and devflow-state.md files. These files contain the necessary audit logs and state data to analyze invoked skills, user gate choices, and overall workflow performance.

Why does my workflow analysis show recurring skill deficiencies across sessions?

Recurring skill deficiencies in workflow analysis indicate potential workflow issues or skill limitations found by comparing data across multiple sessions. It highlights frequently skipped or failed steps, revealing areas where prompt improvements or setting adjustments are needed.

Do I need specific state files to analyze invoked skills and user gate choices?

You need specific state files like devflow-audit.md and devflow-state.md to analyze invoked skills and user gate choices. Parsing these files provides the session summary required to list skill statuses and identify workflow optimization opportunities.