[WHAT] Reverse-engineer any SaaS product into feature inventory + architecture spec + gap map
[HOW] Multi-source extraction → AI enhancement → synthesis against Lev/AgentPing capabilities
[WHEN] "reverse engineer", "build like this", "spec this product", "feature inventory", "how does X work"
[WHY] Fast path from "I saw a cool product" → actionable build plan with effort estimates
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
workflow-reverse-engineer-specs
description
[WHAT] Reverse-engineer any SaaS product into feature inventory + architecture spec + gap map
[HOW] Multi-source extraction → AI enhancement → synthesis against Lev/AgentPing capabilities
[WHEN] "reverse engineer", "build like this", "spec this product", "feature inventory", "how does X work"
[WHY] Fast path from "I saw a cool product" → actionable build plan with effort estimates
/workflow reverse-engineer-specs https://perplexity.ai/ --compare community/agentping --depth deep
Team Structure
Role
Model
Steps
Purpose
scraper
haiku
1-2
Fast discovery and extraction
analyst
sonnet
3-7
Deep synthesis and planning
Technique Map
Multi-source extraction - Combine homepage + docs + API + social for comprehensive understanding
Structured categorization - Sort features by architectural concern (api, ui, infra) for clarity
Effort estimation - Realistic time budgets enable prioritization
Gap mapping - Direct comparison to target module reveals build priorities
Dependency ordering - Phase sequencing prevents blocking work
Evidence preservation - All artifacts saved for team review and iteration
Technique Notes
These techniques improve reverse-engineering accuracy and actionability. Evidence-first approach (scrape real products) beats speculation. Structured output enables handoff between team members. Gap mapping bridges "what exists" to "what we build."
Prompt Architect Overlay
Role Definition
You are the prompt-architect-enhanced specialist for workflow-reverse-engineer-specs, responsible for deterministic extraction and synthesis of product specifications while preserving team handoff patterns.
Input Contract
Required: valid product URL and clear user intent
Preferred: comparison module path if gap mapping desired, depth preference
If ambiguous: clarify scope (architecture understanding vs build planning vs feature inventory)
Output Contract
Structured handoff files at .lev/pm/handoffs/reng-*.md
All session artifacts in ~/.config/LEV/reverse-eng/sessions/<date>/<slug>/
Validation checklist items verified before declaring steps complete
Actionable build plan with effort estimates and dependency ordering
Edge Cases & Fallbacks
If product is private/behind auth: note access limitations and infer from marketing materials only
If API is undocumented: mark as "inferred from UI behavior" and lower confidence
If scope is too broad: suggest phasing extraction (vertical slices vs features)
If compare module doesn't exist: skip gap mapping and note in handoff
