spec-init

Initializes a LiveSpec specification system through a conversational brainstorm and stack decision workflow.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-init-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-init
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-init
Command: npx skills add https://github.com/julien-m/livespec --skill spec-init-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New projects lack a structured specification foundation: stack choices go undocumented, project context lives only in chat history, and AI tools lose track of why decisions were made. This Skill bootstraps a complete .specs/ directory with project profile, stack decisions, ADRs, and testing strategy through a guided interview. ## Core Features & Use Cases - 3-Phase Conversational Setup: Runs a brainstorm interview (Phase A), AI-guided stack decisions with decision trees and mandatory ADRs (Phase B), and automatic .specs/ directory generation (Phase C). - Brainstorm and Design Import: Detects existing brainstorm profiles, mockups, theme CSS, and Penflow contracts, importing them into .specs/design/ with changelog tracking. - From-Code Mode: The --from-code flag reverse-engineers an existing codebase into LiveSpec specs instead of running the interview. - Use Case: A developer starting a freelancer marketplace runs the init flow, answers six questions about users, scale, and real-time needs, and receives a recommended Next.js/Supabase stack with ADRs, a testing strategy, and a ready .specs/ structure. ## Quick Start Ask the AI to initialize LiveSpec in this project and walk you through the brainstorm interview to generate the .specs directory.

Frequently Asked Questions about spec-init

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

FAQPage Schema
How do I initialize a LiveSpec specification system in a new project?

Run the spec-init command, which interviews you with six questions about your project, users, scale, and real-time needs. It then recommends a stack with decision trees, creates ADRs, and generates the full .specs directory structure automatically.

How to generate specs from an existing codebase?

Use the --from-code flag to reverse-engineer an existing codebase into LiveSpec specs instead of running the conversational interview. Autonomous from-code mode for a single-package app must complete within 300 seconds or return a blocked status.

Can spec-init import existing brainstorm or design files?

Yes, it detects brainstorm profiles, mockup PNGs, design source files like .fig or .excalidraw, theme.css, and Penflow contracts from handoff directories. Imported artifacts are copied into .specs/design/ with changelog entries, and the brainstorm source is never referenced again.

What happens if a .specs directory already exists?

The init flow is blocked because the precondition requires no existing .specs directory. You should run the spec-migrate command instead to upgrade a previous installation.

Why are ADRs required during project initialization?

At least one Architecture Decision Record is mandatory before installation proceeds. ADRs document what stack was chosen, which alternatives were considered, and why, so future developers and AI tools understand the reasoning behind each decision.