shipit-kit:new-feature

Automate feature scaffolding by running an init-feature script that generates a standardized specification directory and creates an isolated feature branch. This process applies YAML-first templates and placeholder substitution to establish initial research, plan, and task files.

The best way to create a standardized feature specification is using a scaffolding script that outputs YAML templates and Markdown renders. It automatically establishes a canonical feat/NNN-feature-name branch to ensure a repeatable workflow setup.

Generate YAML-first templates by triggering the spec generation process, which creates a structured NNN-feature-name directory. This scaffolding populates initial files across specs, research, plan, and tasks using placeholder substitution.

Yes, you can use feature branch automation without external dependencies. The scaffolding script requires only a 3-digit number and a kebab-case feature name to generate the branch and specification files.

Initial SDLC scaffolding includes generated YAML templates, Markdown renders, and a standardized feature branch. It sets up the workflow readiness needed to launch the research, plan, and implement lifecycle for the feature.

You need a feature spec scaffold when starting a new feature to reduce manual setup time and ensure a repeatable workflow. It standardizes branch naming and establishes the initial directory structure for isolated work.