aidlc-reverse-engineering
Skill4 starsChanged 6 months agoNo licenceView on GitHub
AI-DLC Reverse Engineering only — analyze an existing codebase and produce architecture, code-structure, API, component-inventory, interaction-diagram, technology-stack, and dependencies documentation. Use when the user wants to understand or document an existing/legacy codebase without committing to the full AIDLC workflow. Trigger on phrases like "analyze this codebase", "document this legacy project", "reverse engineer the architecture", "I want to understand what this code does before changing it", "produce architecture docs for this repo", "onboard me to this project", "what's the architecture of this brownfield app". Stops after RE artifacts are produced — does NOT continue to requirements or coding. For the full workflow including building on the RE output, use `aidlc` or `aidlc-inception`.
In this repository7 other files it gives its agents.
- aidlc-build-and-testSkill
- aidlc-code-generationSkill
- aidlc-constructionSkill
- aidlc-inceptionSkill
- aidlc-requirementsSkill
- aidlcSkill
- aidlc-user-storiesSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

