Instructions for AnkitClassicVision/Claude-Code-Deep-Research: For deep research tasks read Version4/skills/deep-research/SKILL.md and follow Version4/CLAUDE.md; run agents sequentially in isolated contexts when native parallel subagents are unavailable.
Instructions for AnkitClassicVision/Claude-Code-Deep-Research, covering deep research implementation plan, understanding deep research, the 7-phase deep research process, phase 1: question scoping and phase 2: retrieval planning.
Instructions for AnkitClassicVision/Claude-Code-Deep-Research: For deep research tasks read Version4/skills/deep-research/SKILL.md and follow Version4/CLAUDE.md; run agents sequentially in isolated contexts when native parallel subagents are unavailable.
Use this agent to assemble the final report files in Phase 5 and to apply post-gate fixes in Phase 6 of deep research. The editor formats and structures; it never adds facts.
Use this agent to convert scout branch notes into evidence ledger rows. Run at every checkpoint during Phase 3 of deep research, before the convergence log is updated.
Use this agent on the draft report during Phase 5 of deep research, after synthesis and before the gates. Mandatory for Deep and Exhaustive tiers and for any decision-tier claim.
Use this agent when sources conflict on a finding-tier or decision-tier claim, or when stoprule.py returns ESCALATESTUCK. Classifies the conflict and picks a canonical value or declares it unresolved.
Use this agent to execute one research branch: search, fetch, and summarize sources for a single hypothesis. Launch one scout per branch, in parallel. Use proactively during Phase 3 of deep research.
Use this agent to verify finding-tier and decision-tier claims in the evidence ledger during Phase 4 of deep research. Must run on a different model than the one writing the synthesis.
Gate-driven deep research pipeline (V4). Use this skill whenever the user asks for deep research, a research report, due diligence, a literature review, a competitive or market landscape, a technology evaluation, "compare X vs Y with sources", "what does the evidence say about", or any question where the answer will…
Diagnose any AI agent, automation workflow, or proposed agent build against AAC 2.0 and produce a marketing-grade HTML wellness report (Summary view + Process Map view). Always use this skill when the user asks to evaluate, audit, score, diagnose, map, visualize, or "AgentTwin" an AI agent, automation, workflow…
Design or audit an agentic AI workflow with process-first guardrails: deterministic spine, evidence, gates, monitoring, and recovery before autonomy. Use when a user is designing an AI workflow, agent flow, workflow automation, vendor AI deliverable, or autonomy review.
Write specifications precise enough for autonomous AI coding agents to implement without human intervention. Use when: user wants to spec a feature, system, or tool for agent implementation. Do NOT use for: writing code directly (let agents implement), creating skills (use skill-creator).
Diagnose, score, map, visualize, or accept an AI agent or workflow using a public closed-loop readiness report. Use for agent specs, automation workflows, vendor proposals, and agentic builds.
Route prompts by task-demand surface before spending tokens. Use when deciding which model, tool lane, verifier, or human gate a task needs; when a task involves local/private models, small/cheap models, coding, agents, long context, media, compliance, or high-stakes verification.
Universal codebase operations: analyze, organize, and architecturally deepen any repo. Two commands: /organize for read-only analysis and /deepen for multi-agent refactoring. Use when the user wants a codebase scan, deep module scoring, dependency mapping, architectural improvement, or code-to-skill conversion.…
Build three context layers (structural, semantic, philosophical) for a module or service, producing production-ready artifacts: a module manifest, behavioral contracts, and a decision log. Use when: (1) a dark code audit identifies high-risk modules, (2) proactively documenting any critical service, (3) a module's…
Relentlessly interview the user to stress-test a plan, design, docs, or existing codebase before building. Use when the user says "grill me", "grill docs", "grill with docs", wants codebase/domain alignment, wants a CONTEXT.md or ADR-backed interrogation, or needs shared language before implementation.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Use when the user asks to "make sense," "make sense of this," "make it make sense," "this doesn't make sense," or otherwise requests structured comprehension of a confusing idea, decision, plan, document, system, unfamiliar domain, or stuck situation. Produces a visible router, a declared artifact shape, trust-marked…
Use when a user asks whether a new external thing, idea, article, tool, repo, framework, competitor move, workflow, or opportunity is worth caring about now. Runs a memory-first triage, maps where the thing applies, and returns exactly one verdict: GO-now, PARK, or KILL.
Comprehension instrument for AI-mediated work. Triggers when the user says "seeit", "show me the shape", "make this visible", or asks to see/understand/visualize a project, codebase, agent workflow, spec, or AI build at a structural level. Use this skill whenever the user wants to understand the SHAPE of something the…