bmad-quick-spec

This conversational discovery process captures your context and requirements, performs surface-level code investigation, and outputs a structured technical specification document for your small feature.

The best way to document small code changes is to use a specification generation process that combines conversational discovery with code investigation to produce implementation-ready technical documentation outlining requirements, constraints, and the implementation plan.

Yes, you need an existing codebase with known patterns to generate implementation-ready technical specifications, as the process relies on surface-level code scans and requires a user who can provide specific context and requirements for the feature.

Code investigation works by performing surface-level code scans to understand the landscape and existing patterns within your codebase, which then informs the structured technical specification document generated during the conversational discovery process.

You should not use automated specification generation if your codebase lacks established patterns, or if you cannot provide the necessary context and requirements, as the process depends on surface-level code investigation and conversational discovery to produce accurate documentation.