skills.rest
LiorCohen
LiorCohenCOMMUNITY
Explore all skills by this author →
GitHub

component-discovery

Analyze classified requirements to map technical components and document them in SPEC.md.

39|3|Updated Nov 21, 2025
Search Tags:#architecture#documentation#spec-writing#requirements-analysis#discovery-questions#component-discovery#tech-pack
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill component-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: component-discovery
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/tech-discovery
Command: npx skills add https://github.com/LiorCohen/sdd --skill component-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes classified requirements to identify the technical components needed to implement a change, producing a component plan without modifying system files.

Core Features & Use Cases

  • Analyze classified requirements to map them to component types from the active tech pack.
  • Ask targeted follow-up questions to refine scope for each identified component type.
  • Document discovered components in SPEC.md for later planning and validation.
  • Return a components list for inclusion in SPEC.md during the spec-writing phase.

Quick Start

Provide the change details and any classified requirements so I can outline the required components and populate the SPEC.md.

Frequently Asked Questions about component-discovery

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

FAQPage Schema
How do I identify technical components needed from software requirements?▼

Mapping requirements to technical components involves analyzing classified requirements and asking targeted discovery questions to refine scope. Results are documented in SPEC.md to guide later planning and validation phases.

What is the best way to document discovered components for spec writing?▼

Documenting discovered components in SPEC.md captures the mapped component types and refined scope details. This provides a structured component list for specification writing and later validation without modifying system files.

Can I use component discovery to plan system changes without modifying files?▼

Yes, component discovery plans system changes without modifying files. It performs no system changes, returning a components list for specification writing and documenting results in SPEC.md.

Does component discovery work with classified requirements from external spec transformation?▼

Yes, component discovery applies after external spec transformation to guide discovery questions and map classified requirements to component types using tech-pack knowledge, producing a components list.

What are the limitations of using component discovery for architecture planning?▼

A limitation of component discovery for architecture planning is that it performs no system changes and only documents results in SPEC.md. It relies on classified requirements and tech-pack knowledge to return a components list without implementation logic.

Related Skills

Explore More Software Engineering Skills→
kryptobaseddevkryptobaseddev
160

ct-spec-writer

Generate RFC 2119 compliant specifications with structured templates and compliance criteria.

Community
Intermediate
japurcelljapurcell

create-spec

Generate a feature specification and requirements checklist from a feature description.

Community
Advanced
TacuchiTacuchi

spec-refine-loop

Refine ambiguous draft specs into precise, testable requirements via a gap-driven loop.

Community
Advanced
GenuinehGenuineh

docs-specs

Generate structured technical specification documents with defined sections for architecture and APIs.

Community
Intermediate