feature-spec

Generating a feature spec involves running a guided interactive Q&A workflow that captures product requirements and automatically writes the output to a FEATURE_SPEC.md file in your project directory.

Capturing deferred requirements involves recording future enhancements during the Q&A workflow, automatically logging them into a DEFERRED.md file to ensure they are documented without cluttering the main feature scope.

Yes, creating a feature specification requires an AGENTS.md file in the project root directory to provide project context and ensure the generated spec aligns with existing workflows and guardrails.

To start guided feature spec generation, run the command from your project root with the feature name, triggering a structured Q&A session that elicits scope, integration details, and constraints.

Yes, you can trigger a cross-model review after generating a feature spec if a Codex CLI is available in your environment, adding an automated validation layer to the specification process.

Feature specifications are stored under features/<feature-name>/FEATURE_SPEC.md, keeping them organized within your project structure while deferred items are recorded separately in DEFERRED.md.