product-vision-steering

To generate core steering documents, you create three standardized files: product.md, tech.md, and structure.md. This skill establishes consistent, long-lived project context by capturing product vision, approved tech stack, and directory structure guidelines for your team.

Onboarding an existing codebase into SDD workflows requires scanning your current directories to auto-populate tech.md and structure.md. This skill handles that scan automatically, then guides you through defining product.md to align all downstream specification and engineering work.

Feature specifications become misaligned when teams lack consistent, up-to-date core project context. Generating persistent steering documents that capture your approved tech stack, directory layout, and product vision ensures spec authors and engineers share the same foundational understanding.

You need to refresh project steering documents after major changes to your product vision or tech stack. Updating these three core files ensures that downstream spec authors, architects, and engineers remain aligned and prevents inconsistent implementation patterns across the codebase.

Yes, you can standardize directory structure and naming conventions by generating the structure.md steering document. It captures your directory layout, naming conventions, and test placement rules, providing a persistent reference that aligns developer contributions and simplifies onboarding.

You do not need to manually fill out all project context details for a legacy codebase. This skill scans your existing codebase to auto-populate tech.md and structure.md, then guides you through completing product.md to establish full project context without redundant manual entry.