Skill

deep-analyze

Deep-dives initial proposals by researching codebase patterns like naming, DI, and error handling; validates assumptions; outputs implementation roadmap with steps, pseudocode, alternatives table, risks, and immediate actions.

Git

Node

developer-tools

npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flow

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash(git:*)Bash(node:*)WriteAgent

Preview

- Keywords: deep analyze, deep analysis, deep dive, roadmap, deep-analyze

SKILL.md

Similar Skills

feasibility-study

147

Conducts feasibility analysis from first principles: decomposes requirements, analyzes constraints, researches code, explores solutions, discusses with codex, and outputs quantitative comparisons with recommendations. Use before tech specs, for comparisons or risk assessment.

3 files10 tools

sd0x-dev-flow

researching

Explores codebases, researches best practices, evaluates 2-3 approaches with pros/cons, and recommends solutions with codebase-specific reasoning before planning.

orchestrate

Propose

Evaluates if a software idea is worth building and drafts a proposal document using a template if viable. Activates on assess, evaluate, propose, or 'is this worth building' requests.

codagent

Stats

Stars147

Forks20

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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