analyze

Name: analyze
Availability: InStock
Author: lionbenjamin

Analyze development specs, plans, and tasks for traceability and gap detection.

15|6|Updated Jan 5, 2026

Search Tags:#spec #tasks #traceability #plan #analyze #gap-detection

Ready to run

npx skills add https://github.com/lionbenjamin/agent-templates --skill analyze-lionbenjamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/lionbenjamin/agent-templates/tree/main/skills/analyze
Command: npx skills add https://github.com/lionbenjamin/agent-templates --skill analyze-lionbenjamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate development pipelines for alignment between spec, plan, and tasks to prevent rework and miscommunication.

Core Features & Use Cases

Traceability checks: map spec items to plan items and tasks
Gap detection: identify missing coverage between specs, plans, and tasks
Consistency validation: ensure changes propagate across artifacts
Use Case: During planning, ensure every acceptance criterion has a corresponding task.

Quick Start

Run the analyze workflow to verify spec-plan-task alignment before starting implementation.

Frequently Asked Questions about analyze

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

FAQPage Schema

How do I ensure traceability between project specs, plans, and tasks?▼

To ensure traceability between specs, plans, and tasks, analyze your development artifacts to map spec items to corresponding plan items and tasks, validating alignment before coding begins. This prevents rework and miscommunication.

What is spec-plan-task gap detection in software engineering?▼

Spec-plan-task gap detection is the process of identifying missing coverage across development artifacts. It validates that every acceptance criterion within a specification has a corresponding task in the implementation plan.

When do I need to run spec-to-plan consistency validation?▼

You need to run spec-to-plan consistency validation during pre-implementation reviews and planning phases. This ensures changes propagate accurately across artifacts and verifies spec-plan-task alignment before starting implementation.

Can I check if every acceptance criterion has a corresponding task before coding?▼

Yes, you can check if every acceptance criterion has a corresponding task by running an analysis workflow on your development pipeline. This validates spec-plan-task alignment and enforces traceability to prevent rework.

What is the best way to prevent miscommunication between specs and development plans?▼

The best way to prevent miscommunication between specs and development plans is to validate alignment by applying traceability checks and gap detection across artifacts. This ensures changes propagate consistently before implementation.