vibeflow-gen-spec

To generate a technical specification, you provide a feature idea and project context. The Skill outputs a comprehensive spec defining objectives, scope, anti-scope, risks, and dependencies to guide implementation.

A technical specification should include objectives, definitions of done, scope, anti-scope, technical decisions, applicable patterns, risks, and dependencies. This ensures clarity and completeness before implementation begins.

To ensure feature specs adhere to coding standards, the Skill leverages project context and patterns stored in the `.vibeflow/` directory for contextual grounding and convention adherence during generation.

Yes, you can use this spec generation process for any software feature. You supply the feature input, and it resolves applicable patterns and technical decisions based on your specific project context.

The best way to define anti-scope and risks is to automate spec creation. The Skill explicitly isolates out-of-scope elements and identifies potential risks, ensuring alignment with project standards before coding starts.

A technical specification needs a definition of done and technical decisions to provide clear completion criteria and architectural direction. This reduces ambiguity and ensures implementation aligns with project patterns.