project-map-init

Generates a canonical project map file capturing stack, structure, and conventions for SDD workflows.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill project-map-init-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-map-init
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-v2/skills/project-map-init
Command: npx skills add https://github.com/nico0695/ai-tools --skill project-map-init-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working across multiple sessions or phases of a spec-driven development workflow, project context is lost between conversations. This Skill produces a durable, evidence-based project map at .sdd/project-map.md so later phases can recover stack, structure, and conventions without relying on chat memory. ## Core Features & Use Cases - Stack and Tooling Detection: Identifies the package manager, build/test/lint/type-check commands, and stack signals from manifests, lockfiles, and project config. - Shallow Structure Mapping: Captures important directories, maintained docs, and sources of truth without recursively scanning the entire repository. - Convention and Risk Recording: Summarizes evidence-backed conventions and flags repo-specific risks or unusual layout decisions. - Use Case: During sdd-init bootstrap of a new repository, run this Skill to generate .sdd/project-map.md so subsequent exploration and planning phases start with accurate project context. ## Quick Start Generate or refresh the project map for this repository by reading the manifests, config, and top-level docs, then writing the result to .sdd/project-map.md.

Frequently Asked Questions about project-map-init

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

FAQPage Schema
How do I generate a project map for a new repository?▼

Run the project-map-init skill during the sdd-init phase. It reads manifests, lockfiles, build configs, and top-level docs, then writes a structured summary to .sdd/project-map.md covering stack, commands, directories, and conventions.

What information does a project map file contain?▼

The map includes metadata, stack summary, package manager and quality commands, important directories, architecture signals, maintained docs, conventions, and repo-specific risks. It stays concise and evidence-based rather than duplicating full documentation.

When should I refresh the project map?▼

Refresh it when bootstrap is missing, when a refresh is recommended after significant structural changes, or when the user explicitly asks to update project context. It is not a substitute for deeper change-specific discovery.

Does project-map-init scan the entire repository?▼

No. It prefers shallow, high-signal reads of top-level manifests, configs, and docs. It only scans deeper when the repository structure is genuinely ambiguous, keeping the process fast and the output concise.

What happens if project evidence is incomplete?▼

The skill names uncertainty explicitly in the map and returns a partial status when the map is usable but contains unknowns. It returns blocked only when the repository cannot be read reliably or the root is ambiguous.