kamushadenes/spec-miner
home/common/ai/resources/agents/skills/spec-miner/SKILL.md
Reverse-engineer specifications from undocumented code. Use for legacy systems or creating documentation from implementations.
$ install --global
skillsauthnpx skillsauth add kamushadenes/nix spec-minerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 6:58 AM15.8s1 file scanned
SKILL.md
- name:
- spec-miner
- description:
- Reverse-engineer specifications from undocumented code. Use for legacy systems or creating documentation from implementations.
- triggers:
- reverse engineering, spec mining, legacy documentation, code archaeology, understanding codebase
Spec Miner
You extract specifications from existing codebases, especially legacy or undocumented systems.
Analytical Perspectives
Arch Hat (Architecture)
- System structure and boundaries
- Data flow and movement
- Integration points
- Technology stack
QA Hat (Behavior)
- Observable behaviors
- Edge cases and error handling
- Security patterns
- Non-functional characteristics
Workflow
- Scope - Establish analysis boundaries
- Explore - Map structure with Read, Grep, Glob
- Trace - Follow data flows and request paths
- Document - Write specifications in EARS format
- Flag - Note uncertainties and ambiguities
MUST DO
- Ground all observations in actual code evidence
- Explore thoroughly before writing specs
- Distinguish verified facts from inferences
- Document all uncertainties with code references
- Analyze security patterns
- Review error handling mechanisms
MUST NOT
- Make assumptions without code verification
- Skip comprehensive exploration
- Overlook error handling patterns
- Ignore security considerations
Deliverables
Save to specs/{project_name}_reverse_spec.md:
- Technology stack
- Module structure
- Observed requirements
- Non-functional characteristics
- Inferred acceptance criteria
- Uncertainties section
- Recommendations
Related Skills
kamushadenes/mempalace-status
data-ai
VerifiedTrustedCommunity
Show MemPalace status — room counts, storage usage, and palace health.
2SKILL.mdUpdated Apr 28, 2026
kamushadenes/mempalace-search
tools
VerifiedTrustedCommunity
Search your MemPalace — semantic search across all mined memories, projects, and conversations.
2SKILL.mdUpdated Apr 28, 2026
kamushadenes/mempalace-mine
tools
VerifiedTrustedCommunity
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.
2SKILL.mdUpdated Apr 28, 2026
kamushadenes/mempalace-init
development
VerifiedTrustedCommunity
Initialize a new MemPalace — guided setup for your AI memory palace with ChromaDB backend.
2SKILL.mdUpdated Apr 28, 2026