deep-analyze

Analyzes proposals against codebase patterns and produces actionable implementation roadmaps with alternatives.

189|25|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/sd0xdev/sd0x-harness --skill deep-analyze-sd0xdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-analyze
Source: https://github.com/sd0xdev/sd0x-harness/tree/main/skills/deep-analyze
Command: npx skills add https://github.com/sd0xdev/sd0x-harness --skill deep-analyze-sd0xdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating a new proposal without understanding the existing codebase leads to wrong assumptions and wasted implementation effort. This Skill validates a proposal against real code patterns and turns it into a concrete, step-by-step roadmap. ## Core Features & Use Cases - Proposal Validation: Extracts core objectives and key assumptions, then verifies them against the actual codebase. - Code Deep Dive: Researches naming conventions, DI injection patterns, error handling, and similar feature implementations. - Roadmap Generation: Produces immediately actionable implementation steps, alternative comparisons, and risk mitigations. - Use Case: Given a proposal like "Use Redis to cache token prices with TTL 5 minutes", the Skill inspects existing caching and service patterns, then outputs a phased roadmap with file-level changes and an alternatives table. ## Quick Start Ask the agent to deep analyze your proposal, for example by running /deep-analyze followed by the proposal text or a path to a tech spec document.

Frequently Asked Questions about deep-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a feature proposal into an implementation roadmap?▼

Run /deep-analyze with your proposal text or a path to a tech spec file. The Skill validates assumptions against the codebase, researches existing patterns, and outputs phased implementation steps with file-level changes and alternatives.

How to validate technical assumptions before writing code?▼

Deep analysis extracts the proposal's key assumptions and verifies them against actual code, checking naming conventions, DI patterns, and error handling. The result is a validation table showing each assumption, its verification result, and its impact.

When should I use deep analysis instead of a tech spec or feasibility study?▼

Use deep analysis when you have an initial proposal and need codebase-grounded research plus an actionable roadmap. Use /tech-spec for writing specifications, /feasibility-study for go/no-go analysis, and /codex-architect for architecture advice only.

Can deep analysis compare alternative implementation approaches?▼

Yes, the output includes an alternatives table comparing options across dimensions with a recommended choice. It also lists risks with probability and mitigation strategies, plus immediate next actions.

What inputs does the deep-analyze skill accept?▼

It accepts either an inline proposal description as arguments or a file path to an existing document such as a tech spec markdown file. Both are passed to a solution-architect subagent for analysis.