One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-deepinit-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-deepinit
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-deepinit
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-deepinit-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents engineering agents from wasting time re-discovering a codebase by generating consistent, hierarchical context docs when a project starts or its docs are missing or outdated.

Core Features & Use Cases

  • Project discovery via scouting: Delegates structure, tech stack, entry points, tests, and existing documentation detection to an explorer agent.
  • Context synthesis for engineering workflows: Summarizes purpose, architecture, key directories, build/test/run commands, conventions, and known gotchas.
  • Hierarchical context generation: Creates top-level CLAUDE.md and detailed AGENTS.md, plus optional dated architecture documentation under docs/architecture.
  • Use Case: Onboard a new repository after creating the initial scaffolding so engineering agents can plan, code, review, and test with accurate upfront context.

Quick Start

Run the dev-deepinit skill at the root of your new or refactored project so it generates CLAUDE.md and AGENTS.md for engineering agents.

Frequently Asked Questions about dev-deepinit

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

FAQPage Schema
How do I generate CLAUDE.md and AGENTS.md files for a new codebase?

To generate CLAUDE.md and AGENTS.md for a new codebase, run a deep codebase initialization process that scouts repository structure and synthesizes architecture into hierarchical context documents for engineering agents.

What is deep codebase initialization for engineering agent context?

Deep codebase initialization is a process that generates hierarchical project context by discovering structure, synthesizing architecture and conventions, and verifying accuracy so engineering agents operate with full repository understanding from the first session.

When should I regenerate project context documentation for agents?

You should regenerate project context documentation during new project onboarding, when AGENTS.md or CLAUDE.md files are missing, or after a major refactor where existing context docs become invalid and no longer reflect the repository architecture.

What's the best way to onboard an engineering agent to an existing repository?

The best way to onboard an engineering agent is generating hierarchical context docs that summarize purpose, architecture, key directories, build commands, conventions, and known gotchas so the agent can plan, code, review, and test accurately.

Can I generate architecture documentation alongside agent context files?

Yes, alongside top-level CLAUDE.md and detailed AGENTS.md files, the initialization process can optionally generate dated architecture documentation under the docs/architecture directory to provide deeper structural understanding.

Does deep codebase initialization verify the accuracy of generated context docs?

Yes, the initialization process includes an oath-verifier step that checks the accuracy of the synthesized architecture, conventions, and project context before finalizing the CLAUDE.md and AGENTS.md files for engineering workflows.