spec-init

Create a Spec-driven project skeleton with CLAUDE.md, rules, skills, and spec directories.

140|20|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/HHU3637kr/skills --skill spec-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-init
Source: https://github.com/HHU3637kr/skills/tree/main/spec-init
Command: npx skills add https://github.com/HHU3637kr/skills --skill spec-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill initializes a project's Spec-driven infrastructure when starting with Spec, creating CLAUDE.md, .claude/rules/, .claude/skills/, spec/ directory, memory systems, and Obsidian Vault, to provide a ready-to-use baseline for new projects.

Core Features & Use Cases

  • Idempotent setup that creates missing components without overwriting existing content
  • Complete project scaffold including CLAUDE.md, spec/ directory, memory indexes, and Obsidian Vault
  • Quick-start workflow to kick off subsequent spec-start tasks with a single initialization

Quick Start

Run the guided initialization to generate CLAUDE.md, .claude/, spec/, memory systems, and Obsidian Vault.

Frequently Asked Questions about spec-init

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

FAQPage Schema
How do I set up a spec-driven project scaffold with memory and Obsidian integration?

A spec-driven project scaffold requires generating standard directories, memory indexing, and an Obsidian Vault. The initialization creates CLAUDE.md, .claude/rules/, .claude/skills/, and spec/ folders to support the full Spec lifecycle from planning to execution.

What is the best way to initialize project infrastructure without overwriting existing files?

Initializing project infrastructure without overwriting files requires an idempotent setup process. It safely creates missing components like the spec/ directory and memory indexes while ensuring minimal disruption to your existing project content.

How does a spec workflow initialization establish memory indexing for new projects?

Spec workflow initialization establishes memory indexing by creating dedicated memory systems and required directories during project setup. This ensures frontmatter requirements are met and memory indexes are configured to support subsequent spec-start tasks.

Do I need an existing Obsidian Vault to start a Spec-driven workflow?

No, you do not need an existing Obsidian Vault to start a Spec-driven workflow. The initialization process creates a complete project skeleton that generates a new Obsidian Vault and memory systems alongside the required spec/ directory.

Can I run project scaffolding multiple times if my directory structure changes?

Yes, you can run project scaffolding multiple times because the setup is idempotent. It applies at project initialization by safely creating missing components and maintaining frontmatter requirements without breaking your existing spec lifecycle.