epic-scan

Scan a codebase for patterns and components relevant to an epic's domain.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers quickly identify existing code patterns, implementations, and integration points within a codebase that are relevant to a specific epic's domain, preventing redundant work and promoting code reuse.

Core Features & Use Cases

  • Domain-Specific Code Analysis: Focuses on finding code relevant to the epic's scope (e.g., authentication, payments).
  • Pattern Identification: Locates similar features, reusable components, and integration points.
  • Use Case: Before planning an epic to implement a new payment gateway, you can use this Skill to scan the codebase for existing payment-related modules, API integrations, and data models to leverage.

Quick Start

Run the epic-scan skill to analyze the codebase for patterns relevant to the current epic.

Frequently Asked Questions about epic-scan

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

FAQPage Schema
How do I scan an existing codebase for reusable patterns relevant to a new epic?

To scan a codebase for epic relevance, you run an analysis that filters existing implementations based on the epic's domain scope, extracting matching code snippets and identifying integration points for actionable planning recommendations.

What is domain-specific code analysis for epic planning?

Domain-specific code analysis is the process of locating code patterns, similar features, and reusable components within a codebase that match a specific epic's scope, such as authentication or payments, to prevent redundant development work.

How do I find integration points in my codebase before implementing a new feature?

You can find integration points by scanning the codebase for existing API integrations and data models relevant to the epic's domain, which extracts actionable code snippets to help map out where the new feature should connect.

Can I identify reusable components for a specific epic domain like payments?

Yes, you can identify reusable components by filtering codebase findings against the epic's scope, allowing you to locate existing payment-related modules, API integrations, and data models to leverage rather than rebuilding.

Does this code scan approach work without external dependencies?

Yes, this code scan approach works without external dependencies, utilizing internal scripts and reference components to analyze the codebase and extract relevant patterns solely based on the provided epic's domain scope.

What's the best way to prevent redundant work when planning a new epic?

The best way to prevent redundant work is to perform a domain-focused code scan that identifies similar implementations and reusable components, providing actionable recommendations to leverage existing code before starting epic development.