analyze-project

Analyzes AI-assisted coding sessions to classify root causes, rework patterns, and friction hotspots.

1|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill analyze-project-gonzoblasco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-project
Source: https://github.com/gonzoblasco/ai-developer-stack/tree/main/tools-automation/analyze-project
Command: npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill analyze-project-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding sessions often suffer from scope drift, repeated rework, and unclear failures, but teams lack a structured way to understand why. This Skill performs forensic root cause analysis on Antigravity session artifacts to explain what changed, who or what caused it, and what should improve next time. ## Core Features & Use Cases - Session Forensics: Reads conversation artifacts (task.md, implementation_plan.md, walkthrough.md, resolved snapshots) from the Antigravity brain directory to reconstruct what happened in each session. - Root Cause Classification: Assigns primary causes such as SPEC_AMBIGUITY, HUMAN_SCOPE_CHANGE, REPO_FRAGILITY, AGENT_ARCHITECTURAL_ERROR, VERIFICATION_CHURN, or LEGITIMATE_TASK_COMPLEXITY, each with evidence and confidence levels. - Severity Scoring & Hotspots: Scores sessions 0-100 across completion, replanning, scope instability, and rework dimensions, and clusters friction by file or subsystem. - Use Case: After a week of AI-assisted development with heavy rework, run this Skill to generate a session_analysis_report.md showing that most churn came from ambiguous opening prompts, then rewrite your prompt templates accordingly. ## Quick Start Analyze my recent Antigravity sessions and generate a root cause report explaining why sessions required rework.

Frequently Asked Questions about analyze-project

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

FAQPage Schema
How do I analyze why my AI coding sessions required rework?▼

Run the analysis workflow against your Antigravity brain directory, which reads task.md, implementation_plan.md, and walkthrough.md artifacts per session. It classifies each session's rework shape and assigns a primary root cause with evidence and confidence levels.

What root causes does session analysis detect?▼

It distinguishes six primary causes: SPEC_AMBIGUITY, HUMAN_SCOPE_CHANGE, REPO_FRAGILITY, AGENT_ARCHITECTURAL_ERROR, VERIFICATION_CHURN, and LEGITIMATE_TASK_COMPLEXITY. Each diagnosis includes supporting evidence and a High, Medium, or Low confidence rating.

How is prompt quality evaluated in session analysis?▼

The opening request is scored 0-2 on six dimensions: clarity, boundedness, testability, architectural specificity, constraint awareness, and dependency awareness. These scores feed into severity scoring and cohort comparisons between successful and re-planned sessions.

What output does the session analysis produce?▼

It generates a session_analysis_report.md in the project directory containing an executive summary, root cause breakdown, prompt sufficiency analysis, friction hotspots, and recommendations with evidence and expected benefits.

When should I not use session root cause analysis?▼

It is not useful when sessions lack stored artifacts in the Antigravity brain directory, since evidence precedence favors artifact contents over inference. Single clean sessions with no rework also yield little diagnostic value.