product-type-detector

Detect product types from user requirements to guide architecture depth sections.

2|1|Updated Feb 7, 2026

Search Tags:#architecture #requirements #blueprint #detect #product-type #depth-section

Ready to run

npx skills add https://github.com/navraj007in/architecture-cowork-plugin --skill product-type-detector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-type-detector
Source: https://github.com/navraj007in/architecture-cowork-plugin/tree/main/skills/product-type-detector
Command: npx skills add https://github.com/navraj007in/architecture-cowork-plugin --skill product-type-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically identifies product types from user requirements to guide domain-specific architecture depth sections.

Core Features & Use Cases

Automatic product-type detection from requirements to classify into multiple types.
Supports depth-section injection into blueprints based on detected types.
Use Case: Provide a complex requirement like 'real-time collaboration with multi-tenant' to see how types map to architecture depth.

Quick Start

Provide a user requirements paragraph to the detector and receive a list of detected product types along with recommended depth sections.

Frequently Asked Questions about product-type-detector

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

FAQPage Schema

How do I detect product types from user requirements for architecture blueprints?▼

To detect product types from user requirements, you provide a requirements paragraph to the detector, which automatically classifies them and returns a structured list of types to drive domain-specific architecture depth sections.

Can I detect multiple product types for a single complex requirement?▼

Yes, product type detection applies across multi-type scenarios. If you provide a complex requirement like real-time collaboration with multi-tenant, the detector returns all applicable types to guide downstream blueprint generation.

How do I map domain-specific architecture depth sections to detected product types?▼

You map architecture depth sections by using the structured list of detected product types returned by the detector. This list directly drives and prioritizes domain-specific depth injection into your architecture blueprints.

What is the best way to automate architecture depth section prioritization?▼

Automating architecture depth prioritization involves passing user requirements to a product type detector. The detector outputs all applicable product types, which you use to sequence and generate domain-specific depth sections for your blueprints.

Does product type detection work with multi-tenant and real-time collaboration requirements?▼

Yes, product type detection works with multi-tenant and real-time collaboration requirements. It accurately identifies these specific scenarios from your input text and maps them to the appropriate architecture depth sections.

Why does my architecture blueprint lack domain-specific depth sections?▼

Your architecture blueprint lacks domain-specific depth sections because product types were not detected from your initial requirements. Running a detector identifies these types to inject and prioritize the necessary domain-specific depth.