shep-kit:new-feature

To scaffold a spec-driven workflow, you can generate a complete specification directory with initial YAML templates and a dedicated feature branch. This creates a ready-to-run workspace enforcing a YAML-first process for feature planning.

Standardizing feature specification requires templates for spec, research, plan, tasks, and feature state. These YAML files structure the initial project details and auto-generate corresponding Markdown artifacts for documentation.

Yes, pnpm is required as a dependency to run the scripts that generate your feature spec workspace. The scaffolding process relies on this package manager to execute the workflow setup.

You create a dedicated branch and spec directory by running a scaffolding command that wires the branch automatically. This provisions a ready-to-edit workspace where teams can collaborate on YAML templates.

Yes, you can use this scaffolding tool whenever you revamp an existing feature. It generates a fresh specification directory and populates new YAML templates to restart the spec-driven process.

The best way to start a feature with a YAML-first approach is generating initial spec, research, plan, and tasks templates. This ensures consistency by populating structured YAML files before generating Markdown documentation.