sd0xdev/deep-analyze
skills/deep-analyze/SKILL.md
Deep-dive analysis of an initial proposal — research code implementation, produce an actionable roadmap and alternatives
$ install --global
skillsauthnpx skillsauth add sd0xdev/sd0x-dev-flow deep-analyzeInstall 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, 4:05 AM76.5s1 file scanned
SKILL.md
- name:
- deep-analyze
- description:
- Deep-dive analysis of an initial proposal — research code implementation, produce an actionable roadmap and alternatives
- allowed-tools:
- Read, Grep, Glob, Bash(git:*), Bash(node:*), Write, Agent
Deep Analyze
Trigger
- Keywords: deep analyze, deep analysis, deep dive, roadmap, deep-analyze
When NOT to Use
- Architecture advice only (use
/codex-architect) - Tech spec writing (use
/tech-spec) - Feasibility analysis (use
/feasibility-study)
Agent Dispatch
Agent({
description: "Deep-dive analysis with actionable roadmap and alternatives",
subagent_type: "solution-architect",
prompt: `Perform a deep analysis of the following initial proposal.
Follow the analysis framework and output format defined in this skill.`
})
Task
Input
$ARGUMENTS
Analysis Flow
Phase 1: Understand & Validate
- Extract the core objectives of the initial proposal
- Identify key assumptions (which may be wrong)
- List technical points that need verification
Phase 2: Code Deep Dive
Research the existing codebase thoroughly. Must verify:
- Naming conventions
- DI injection patterns
- Error handling patterns
- Implementation patterns of similar features
Phase 3: Roadmap Output
Based on the research, produce:
- Implementation steps (immediately actionable)
- Key pseudocode (only core 1-3 lines, omit if not necessary)
- Alternative comparison
Output
# [Proposal Name] Implementation Roadmap
## Proposal Validation
| Assumption | Verification Result | Impact |
## Code Research Summary
| Module | Existing Implementation | Reusable |
## Implementation Roadmap
### Step 1: [Title]
**Objective**: One sentence
**Files**: `src/xxx.ts` (modify/create)
## Alternatives
| Dimension | Option A (Recommended) | Option B |
## Risks & Mitigations
| Risk | Probability | Mitigation |
## Immediate Actions
1. [ ] First task
2. [ ] Second task
Examples
/deep-analyze "Use Redis to cache token prices with TTL 5 minutes"
/deep-analyze docs/features/xxx/tech-spec.md
Related Skills
sd0xdev/zh-tw
documentation
VerifiedTrustedCommunity
Rewrite the previous reply in Traditional Chinese
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/watch-ci
development
VerifiedTrustedCommunity
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/verify
development
VerifiedTrustedCommunity
Verification loop — lint -> typecheck -> unit -> integration -> e2e
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/update-docs
development
VerifiedTrustedCommunity
Research current code state then update corresponding docs, ensuring docs stay in sync with code.
147SKILL.mdUpdated Apr 28, 2026