sdd-spec-init

Generate a date-prefixed feature name and initialize spec.json and requirements.md templates.

Updated Dec 2, 2025
One-click install
npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-spec-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec-init
Source: https://github.com/qlawmarq/dotfiles-common/tree/main/skills/sdd-init/references/skills/spec-init
Command: npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-spec-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the initial setup for Spec-Driven Development (SDD) by creating the necessary directory structure and metadata files for a new feature specification, ensuring a consistent and organized starting point.

Core Features & Use Cases

  • Feature Name Generation: Creates a unique, date-prefixed feature name based on a project description.
  • Directory Structure Creation: Initializes a docs/tasks/todo/ directory for the new specification.
  • Template-Based File Initialization: Populates spec.json and requirements.md using predefined templates with relevant placeholders.
  • Use Case: When starting a new feature like "implement user authentication," this skill will create the foundational files and structure, ready for detailed requirements to be added.

Quick Start

Use the sdd-spec-init skill to initialize a new specification for a feature that allows users to reset their passwords.

Frequently Asked Questions about sdd-spec-init

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

FAQPage Schema
How do I initialize a spec-driven development project for a new feature?▼

To initialize spec-driven development, this Skill generates a unique, date-prefixed feature name from your project description and creates the required directory structure with populated spec.json and requirements.md files.

What files are generated when setting up a new feature specification?▼

Setting up a new feature specification generates a spec.json metadata file and a requirements.md document using predefined templates within a newly created docs/tasks/todo/ directory structure.

How do I standardize project setup for feature development documentation?▼

Standardize project setup for feature development by using template-based file initialization to populate spec.json and requirements.md, ensuring a consistent starting point and organized directory structure for every new specification.

Does this initialization process handle writing detailed feature requirements?▼

No, the initialization process does not handle writing detailed feature requirements; it adheres to strict phase separation by only performing setup tasks and populating templates with relevant placeholders.

Can I automate directory structure creation for spec-driven development workflows?▼

Yes, you can automate directory structure creation for spec-driven development workflows; this Skill creates the necessary docs/tasks/todo/ directories and metadata files automatically from a simple project description input.