skills.rest
oleyna80
oleyna80COMMUNITY
Explore all skills by this author →
GitHub

technical-discovery

Analyzes project structure and artifacts to identify gaps, duplicates, and blockers.

Updated Jun 12, 2026
Search Tags:#planning#discovery#gap analysis#project analysis#ripgrep#read-only#file inventory
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill technical-discovery-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-discovery
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/technical-discovery
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill technical-discovery-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before planning or implementing work, teams often lack a clear picture of what already exists in a repository. This Skill performs a read-only inventory of project files and key documents, surfacing gaps, duplicates, and blockers so decisions are grounded in actual artifacts rather than assumptions. ## Core Features & Use Cases - File Inventory: Enumerates project files using ripgrep and standard shell tools to build a complete picture of the codebase. - Document Review: Reads key documents such as strategy, brand, ops, and AI configuration files to understand current state. - Gap and Blocker Analysis: Identifies missing pieces, duplicated content, and blockers, optionally producing a short RFC or recommendations in docs/research/. - Use Case: Before decomposing a new feature into tasks, run this Skill to confirm which components already exist, which documents govern the area, and what is missing. ## Quick Start Ask the agent to explore and analyze the current project structure and report what already exists, including gaps and blockers.

Frequently Asked Questions about technical-discovery

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

FAQPage Schema
How do I analyze an existing project structure before starting new work?▼

Run a discovery pass that inventories files with rg --files, reads key governance and strategy documents, and reports gaps, duplicates, and blockers. This Skill performs exactly that read-only analysis and links every finding to specific files.

What tools are used for project file inventory and discovery?▼

This Skill uses ripgrep (rg), find, grep, ls, cat, jq, and git for read-only inspection. These shell tools enumerate files and search content without modifying the repository.

Can this Skill modify code or project files during analysis?▼

No. The Skill is strictly read-only and constrained to analysis only. It may optionally create a short RFC or recommendations document in docs/research/, but it never edits existing code or content.

What happens after the technical discovery analysis is complete?▼

Once inventory, gaps, and blockers are documented, the workflow hands off to task decomposition or Control Tower planning. The handoff auto-proceeds on success with no hard stop.

When should I not use a discovery analysis skill?▼

Skip it when the project state is already well documented and traceable, or when you need implementation rather than analysis. This Skill only inspects and reports; it does not write or refactor code.

Related Skills

Explore More Software Engineering Skills→
icliniciclinic
9

design

Translate vague ideas into formal technical designs with JIRA and Figma context.

Official
Advanced
sddevelopment-besddevelopment-be
13

status

Generates executive status reports summarizing repository progress, task queues, blockers, and milestone health.

Official
Intermediate
SteveGJonesSteveGJones
3

methodology-compliance-check

Generate structured compliance reports identifying AI architecture governance gaps against the AI-First BSA methodology.

Community
Advanced
mqzkimmqzkim

code-review

Review code for architecture, security, performance, and concurrency issues.

Community
Advanced