Does this skill modify my source code?

No, the Technical Discovery skill is strictly read-only. It is designed to provide analysis, research, and documentation without making any implementation changes.

How does it research external libraries or APIs?

It utilizes tools like Perplexity and WebSearch to find up-to-date documentation, community best practices, and known issues related to external technologies.

When should I use Technical Discovery instead of a standard coding task?

Use it when you need to understand the 'how' or 'where' of a complex change, or when you need to assess risks and dependencies before starting the actual work.

What kind of output can I expect?

The skill generates a structured markdown report containing a summary, codebase analysis, external findings, impact assessment, and clear recommendations.

Technical Discovery

Name: Technical Discovery
Author: langadventurellc

bylangadventurellc

0•

コラボレーションツール

Conducts deep codebase research and technical impact analysis to scope projects and investigate issues without modifying code.

The Technical Discovery skill empowers Claude to act as a technical architect and researcher, performing comprehensive analysis of your codebase and external documentation before any implementation begins. It is designed to answer complex questions about system architecture, identify necessary change points for new features, and assess risks or dependencies. By leveraging advanced search tools, codebase exploration agents, and external research via Perplexity, it produces a detailed, structured report that informs decision-making and project scoping, ensuring a clear roadmap is established before writing a single line of code.

主な機能

010 GitHub stars

02Comprehensive impact assessment identifying affected components and dependencies

03External technical research via Perplexity for documentation and best practices

04Structured discovery reports including risk analysis and trade-offs

05Deep codebase exploration using targeted search and autonomous subagents

06Proactive clarification to resolve ambiguous requirements before research begins

ユースケース

01Investigating the root cause of complex architectural bottlenecks or bugs

02Scoping a new feature to understand which files and systems will be affected

03Researching third-party library integrations and implementation patterns

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add langadventurellc/claude-marketplace technical-discovery

For use in Claude.ai and ChatGPT

Download Skill