draft-product-spec

Drafting a product specification from intent involves synthesizing product identity, behavioral invariants, scope boundaries, and vertical-slice features into a structured features.yaml artifact. This approach strictly excludes technology names, implementation patterns, and deployment platforms to keep the output stakeholder-focused.

Creating a features.yaml artifact for early product discovery requires synthesizing your product intent into end-to-end vertical-slice features. The process outputs a schema-conformant YAML file capturing the product scope boundaries and behavioral rules without locking in specific technologies.

You can enrich your product specification using optional vision.md and roadmap epic artifacts. These inputs provide additional context for defining behavioral invariants and scope boundaries, but they act as enrichment rather than mandatory gates for generating the features.yaml output.

Defining scope boundaries and behavioral invariants for stakeholder review is best achieved by structuring product intent into a schema-conformant features.yaml. This captures what the product does and the rules it must honor while stripping out specific technology references and deployment patterns.

Your generated product specification excludes technology, SDK references, and database products to maintain a strict stakeholder focus. This constraint ensures the features.yaml artifact defines only the product identity and behavioral rules without prematurely locking in implementation details.

Generating a features.yaml does not overwrite locked product artifacts. The drafting process specifically targets the output base path to write the schema-conformant YAML file while preserving any existing LOCKED artifacts within your repository.