speckit-specify

To generate feature specifications from natural language, you input a feature idea like a dark mode toggle to automatically create user stories, functional requirements, and acceptance criteria. This process outputs a structured spec.md file detailing all necessary project requirements.

Yes, you can automatically determine Git branch names from new feature requirements by generating a specification that suggests concise, descriptive branch names. For example, a feature description for a dark mode toggle will produce a branch named 1-dark-mode-toggle.

Yes, you need a .specify/ directory within your project structure to manage spec files for user stories. This specific directory is required for operations that generate and update feature specifications using spec-driven development methodologies.

The best way to write acceptance criteria and functional requirements for feature development is to use an automated specification generation tool. It streamlines the initial phase by parsing natural language descriptions to ensure clarity and consistency across your project.

You can update existing feature specifications with new user stories by processing revised natural language descriptions through your spec generation tool. This automatically modifies and manages your spec files within the project structure to reflect new requirements.