One-click install
npx skills add https://github.com/dpaola2/pipeline-skills --skill discovery-dpaola2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery
Source: https://github.com/dpaola2/pipeline-skills/tree/main/.claude/skills/discovery
Command: npx skills add https://github.com/dpaola2/pipeline-skills --skill discovery-dpaola2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps understand the current state of a codebase before designing changes, by exploring files, APIs, and platform specifics.

Core Features & Use Cases

  • Codebase Exploration: Analyzes existing code, models, controllers, and serializers relevant to a feature.
  • API & Platform Analysis: Documents current API endpoints, response shapes, and cross-platform patterns.
  • Risk Identification: Flags technical risks, performance concerns, and security issues.
  • Use Case: Before adding a new feature to an existing application, run this Skill to get a comprehensive report on how similar functionalities are implemented and identify potential technical hurdles.

Quick Start

Run the discovery skill for the project identified by the callsign SN-3.

Frequently Asked Questions about discovery

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

FAQPage Schema
How do I analyze a codebase before designing new features?

To analyze a codebase before designing new features, you can run a discovery process that explores existing files, models, and controllers to produce a detailed technical assessment report. This flags technical risks and documents open questions across specified platforms.

What is a discovery report in software architecture?

A discovery report in software architecture is a comprehensive document detailing the current state of a codebase. It parses PRDs, searches API documentation, identifies technical risks, and documents open questions to guide subsequent architectural design decisions.

How do I identify technical risks in an existing API?

You can identify technical risks in an existing API by performing a codebase exploration that documents current endpoints, response shapes, and cross-platform patterns. This process flags performance concerns and security issues for architectural review.

Can I document cross-platform API patterns using codebase analysis?

Yes, codebase analysis can document cross-platform API patterns by exploring existing code and API documentation. It maps current endpoints and response shapes across specified platforms to ensure architectural consistency before implementing new functionalities.

What is the best way to document open questions for a technical assessment?

The best way to document open questions for a technical assessment is to run an automated discovery process that parses PRDs and searches code. It systematically aggregates these questions into a detailed discovery report alongside identified technical risks.

Does codebase exploration work for understanding existing serializers and models?

Yes, codebase exploration works for understanding existing serializers and models by analyzing the current application state. It reviews these components to document how similar functionalities are implemented before architectural changes are applied.