dan:init

Create a DAN project workspace with planning files and configuration.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/RavBogard/DAN --skill dan-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dan:init
Source: https://github.com/RavBogard/DAN/tree/main/.claude/skills/dan-init
Command: npx skills add https://github.com/RavBogard/DAN --skill dan-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the initial setup for a DAN-managed project, eliminating manual creation of planning directories and standard files and reducing setup time.

Core Features & Use Cases

  • Creates the .planning/ directory with PROJECT.md, STATE.md, ROADMAP.md, REQUIREMENTS.md, and CONTEXT.md to standardize project framing.
  • Generates .planning/dan.config.json with sensible defaults to bootstrap the workflow.
  • Transitions into the dan:discuss phase to capture project intent through an interactive interview.

Common use cases include starting new projects quickly, enforcing a consistent planning structure, and enabling immediate discussion-based requirements gathering.

Quick Start

Initialize a new DAN project to create the planning directory and enter the discuss phase.

Frequently Asked Questions about dan:init

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

FAQPage Schema
How do I initialize a project workspace with a standard planning directory structure?

To initialize a project workspace, this skill automates creating a `.planning` directory structure containing standard files like PROJECT.md and ROADMAP.md, reducing manual setup time. It generates a default dan.config.json to bootstrap the workflow.

What files are needed to standardize project framing and capture project intent?

Standardizing project framing requires PROJECT.md, STATE.md, ROADMAP.md, REQUIREMENTS.md, and CONTEXT.md files. These capture project intent and are generated automatically within the `.planning` directory upon initialization.

How do I start capturing requirements through a discuss phase for new project management?

Starting requirements gathering involves initializing the DAN project workspace, which automatically transitions into the dan:discuss phase. This interactive interview quickly captures project intent right after the standard files are created.

Can I bootstrap a workflow with sensible defaults for project planning?

Yes, you can bootstrap a workflow with sensible defaults. The initialization process generates a `dan.config.json` file within the `.planning` directory, applying standard configurations to bootstrap the project workflow immediately.

What is the best way to enforce a consistent planning structure across new projects?

The best way to enforce consistent planning structure is automating the initial setup. This creates the standard `.planning` directory with required planning files and sensible workflow defaults, eliminating manual creation and ensuring uniformity.

Do I need to manually create planning directories before starting project initialization?

No, you do not need to manually create planning directories. The initialization skill automates the setup of the `.planning` directory and its standard files, eliminating manual creation and reducing setup time.