feature-setup

To create a git worktree and feature branch with documentation templates, run the feature setup workflow to automatically establish an isolated workspace, generate a dedicated branch, and scaffold PRD and workplan documents in a standardized docs directory for immediate development.

Scaffolding PRD and workplan docs is best handled by a definition-driven workflow that generates a standardized docs directory structure, populating templates from an existing feature-definition file or creating blank ones to ensure immediate PR readiness.

Yes, you can use an existing feature definition to populate documentation templates by placing a feature-definition markdown file at the expected temporary path, which the setup process reads to automatically fill in the PRD and workplan skeletons.

Setting up isolated worktrees prevents cross-contamination between feature tasks by creating a distinct, dedicated workspace per feature, ensuring that branch dependencies and file changes remain completely separated until merged.

Documentation scaffolding for git branch workflows works by automatically generating a standardized directory structure with template files for the PRD, workplan, README, and implementation summary, ensuring consistent readiness across isolated feature branches.

You do not need to manually create a docs directory structure for every new feature because the setup process automatically generates the required nested folders and template files, enforcing a consistent readiness process across all projects.