recipe-reverse-engineer
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
npx skills add shinpr/claude-code-workflows --skill recipe-reverse-engineer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before making workflow decisions, invoking agents, or resolving findings. **Context**: Reverse engineering workflow to create documentation from existing code Target: $ARGUMENTS ## Orchestrator Definition **Core Identity**: "I am an orchestrator." **Local authority gate**: Make this recipe's workflow decisions and validate each returned result directly; delegate semantic deliverable production to the named specialist. **Review Resolution Gate [MANDATORY]**: Resolve every actionable deliverable-review finding through subagents-orchestration-guide `Review Resolution` before correction or progression. Before the first finding disposition, read `references/review-resolution.md` from the loaded subagents-orchestration-guide skill. **Execution Protocol**: 1. **Invoke named specialists for deliverable production** — pass deliverable paths between them and validate their results (see subagents-orchestration-guide "Orchestrator Execution Boundary") 2. **Process one step at a time**: Execute steps sequentially within each unit (2 → 3 → 4 → 5). Each
- Orchestrator Definition
- Step 0: Initial Configuration
- 0.1 Scope Confirmation
- 0.2 Output Configuration
- Workflow Overview
- Phase 1: PRD Generation
- Step 1: PRD Scope Discovery
- Step 2-5: Per-Unit Processing
- Phase 2: Design Doc Generation
- Step 6: Design Doc Scope Mapping
- Step 7-10: Per-Unit Processing
- Final Report
- Error Handling
What does the recipe-reverse-engineer skill do?
Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow
How do I install it?
Run `npx skills add shinpr/claude-code-workflows --skill recipe-reverse-engineer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From shinpr/claude-code-workflows, a repository with 664 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.