technical-discovery

Name: technical-discovery
Availability: InStock
Author: langadventurellc

Research problems and proposed changes to identify affected components and dependencies.

Updated Jan 18, 2026

Search Tags:#architecture #research #risk-assessment #issue-triage #codebase-analysis #technical-discovery

Ready to run

npx skills add https://github.com/langadventurellc/claude-marketplace --skill technical-discovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technical-discovery
Source: https://github.com/langadventurellc/claude-marketplace/tree/main/plugins/task-trellis/skills/technical-discovery
Command: npx skills add https://github.com/langadventurellc/claude-marketplace --skill technical-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured technical discovery by researching problems or proposed changes and delivering a comprehensive, non-implementation-based analysis to inform decisions and issue creation.

Core Features & Use Cases

Structured Research: Define scope, gather relevant context, and map dependencies and impact across the codebase.
Contextual Analysis: Produce findings that highlight risks, trade-offs, and potential change points to guide planning.
Use Case: When evaluating a feature proposal, run a technical discovery to understand required work, impacted components, and evidence-driven recommendations before writing a Trellis issue.

Quick Start

Provide the problem or question and optional context; request a structured discovery report.

Frequently Asked Questions about technical-discovery

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

FAQPage Schema

How do I assess codebase impact and dependencies before starting a new feature?▼

Technical discovery assesses codebase impact by mapping affected components and dependencies to define scope. It researches a proposed change without writing implementation code, identifying risks and trade-offs to produce evidence-driven findings for planning.

What is the best way to research architecture questions and identify potential risks?▼

Architecture research and risk identification are conducted by gathering contextual codebase analysis to map dependencies. This process highlights change points and trade-offs, delivering structured, evidence-based findings that guide technical decisions.

Can I scope a proposed change and define issues without writing implementation code?▼

Yes, you can scope proposed changes by running a non-implementation research phase. This analysis defines the problem, identifies affected system components, and produces actionable recommendations, ensuring issues are fully scoped before development begins.

How do I structure a technical discovery report for issue triage?▼

A technical discovery report structures issue triage by defining the problem scope, mapping dependencies, and listing evidence-based findings. It guides issue creation by detailing potential risks, trade-offs, and actionable recommendations for the codebase.

Does technical discovery require any specific frameworks or dependencies to run?▼

No, technical discovery requires no external dependencies or specific frameworks. You provide the problem or question and optional additional context, and it delivers a structured analysis of your codebase architecture and risks.

When should I not use a structured technical discovery for my project?▼

You should avoid structured technical discovery when you need actual implementation rather than research, or when a problem is trivial and requires no risk assessment. It is designed for comprehensive codebase reconnaissance, not writing code.