Spec Init

What it does

The Spec Init skill rapidly generates initial project structures and configurations for new requirements within a repository. It creates a new branch with a three-digit numerical prefix and kebab-case short name, sets up the corresponding directory structure under .aisdlc/specs/{num}-{short-name}/, and writes the original requirement text into requirements/raw.md (encoded as UTF-8 with BOM). This streamlines development setup and saves time by automating repetitive tasks.

When to use it

• Starting a new "requirement" where no branch or directory structure exists yet.
• When provided with Chinese requirement text, avoiding potential encoding issues during manual file creation.
• Ensuring consistent branch naming, numbering, and directory structures according to repository conventions.
• To quickly establish the foundational project layout for a new specification.

Key capabilities

• Creates new branches named {num}-{short-name} (three-digit number, kebab-case short name).
• Generates a standardized .aisdlc/specs/{num}-{short-name}/ directory structure with requirements, design, implementation, verification, and release subdirectories.
• Writes the original requirement text to requirements/raw.md using UTF-8 encoding with BOM.
• Supports both PowerShell (Windows) and Bash (macOS/Linux) execution environments.
• Automatically deletes the source file after successful script execution.

Example prompts

• "Create a new Spec Pack for this requirement text, saving it as a file." (The agent will write the text to a temporary file.)
• "Initialize a new spec with short name 'export-orders' based on the content of /path/to/requirement.txt."
• "Start a new specification using the provided requirements document located at /tmp/new_spec.md."

Tips & gotchas

• File Paths Required: The skill requires the requirement to be passed as a file path, either directly or by writing it to a temporary file. This avoids encoding issues with Chinese characters.
• Source File Deletion: The original source file (whether provided or temporary) will be automatically deleted after script execution. Back up any critical content beforehand.
• Submodule Handling: The skill initializes Spec branches only in the root project; it does not create branches within submodules during this phase.