project-analyze

Analyze project plans, PRDs, and epics for alignment, coherence, feasibility, and risks.

2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/telum-ai/speck --skill project-analyze-telum-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-analyze
Source: https://github.com/telum-ai/speck/tree/main/.cursor/skills/project-analyze
Command: npx skills add https://github.com/telum-ai/speck --skill project-analyze-telum-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies inconsistencies, gaps, and feasibility issues in project plans, PRDs, and epic structures before development begins, preventing costly rework.

Core Features & Use Cases

  • Strategic Alignment Check: Ensures project vision, goals, and scope are consistent.
  • Epic Coherence Validation: Verifies logical epic boundaries, dependencies, and value delivery.
  • Scope Feasibility Assessment: Checks if the total scope aligns with estimates and resources.
  • Requirement Traceability: Maps PRD requirements to epics and checks for completeness.
  • Risk Identification: Highlights critical risks, bottlenecks, and technical unknowns.

Quick Start

Run /project-analyze to check the current project's planning documents for issues.

Frequently Asked Questions about project-analyze

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

FAQPage Schema
How do I check PRD requirements traceability and epic coherence before development?

To check PRD requirements traceability and epic coherence, analyze project planning artifacts to map requirements to epics, verify logical boundaries, and validate dependencies to ensure consistent value delivery.

What is scope feasibility assessment in project planning?

Scope feasibility assessment is the process of validating whether total project scope aligns with scale estimates and resources, checking PRDs and epics to identify gaps before development begins.

How do I identify critical risks and technical unknowns in a project plan?

To identify critical risks in a project plan, perform a multi-dimensional analysis against defined templates to highlight bottlenecks, technical unknowns, and strategic misalignment, generating a report with severity classifications.

Can I validate epic boundaries and strategic alignment for large scale project plans?

Yes, you can validate epic boundaries and strategic alignment for large scale plans by checking project vision, goals, and scope consistency, ensuring epics deliver value without overlapping dependencies.

What's the best way to review a PRD for requirement coverage and scope feasibility?

The best way to review a PRD for requirement coverage is to perform multi-dimensional analysis that validates requirement traceability, assesses scope feasibility, and outputs actionable fix commands for identified gaps.

Why does my project plan have requirement coverage gaps and epic dependency issues?

Project plans have requirement coverage gaps when PRD requirements lack traceability to epics, and epic dependency issues arise from incoherent boundaries, both identifiable through early scope feasibility analysis.