init

Analyze codebases to generate and populate spec documents.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill init-byeongminlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/ByeongminLee/nextjs-claude-code/tree/main/template/.claude/skills/init
Command: npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill init-byeongminlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes a codebase after installation and automatically generates and populates the core spec documents (spec/PROJECT.md, spec/ARCHITECTURE.md, spec/rules/, and initial draft feature specs) to kick off documentation-driven development.

Core Features & Use Cases

  • Analyzes the repository structure to generate baseline spec files and doc scaffolding.
  • Creates spec/PROJECT.md, spec/ARCHITECTURE.md, spec/rules/, and initial draft feature specs for fast onboarding.
  • Supports integration with existing workflows to ensure documentation stays in sync with code.

Quick Start

Run the init skill after installing FeatureSpec to analyze the repository and populate the initial spec docs.

Frequently Asked Questions about init

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

FAQPage Schema
How do I auto-generate spec docs from an existing codebase?

To auto-generate spec docs from a codebase, you can use a repository scanning tool that analyzes the structure and populates core spec files like spec/PROJECT.md and spec/ARCHITECTURE.md automatically without manual input.

What is the best way to initialize spec-driven development for a legacy project?

Initializing spec-driven development for a legacy project is best handled by running an automated discovery tool that scans the repository and generates baseline spec scaffolding alongside initial draft feature specs.

Can I populate spec documents without providing external configuration inputs?

Yes, you can populate spec documents without external inputs because the initialization process relies entirely on analyzing the existing codebase structure to generate documentation.

Does automated repository scanning work for both new repos and legacy codebases?

Automated repository scanning works for both new repositories and legacy codebases, analyzing the existing structure to generate baseline spec files and kick off documentation-driven development.

What spec files are created when initializing documentation from a repository?

When initializing documentation from a repository, the scanning process creates spec/PROJECT.md, spec/ARCHITECTURE.md, spec/rules/, and initial draft feature specs to establish fast onboarding scaffolding.