specify-scenario

To turn business intents into actionable scenarios, you analyze the intent against existing context and generate INSERT, MODIFY, DELETE, or REFER scenes. These template-driven scene definitions are then appended to spec.md to ensure traceability and support review.

Scenario traceability in spec management links generated scenes to original business intents. Change auditing works by appending template-driven INSERT, MODIFY, or DELETE actions to spec.md, ensuring all modifications are tracked for collaboration and review.

To generate INSERT and MODIFY scenes, provide the new business intent alongside existing context.md documents. The system analyzes the intent against current scenarios, identifies necessary changes, and appends the generated scenes to spec.md.

Yes, existing context.md and related documents are required to generate requirements specs. The system applies context-aware analysis to align new business intents with current scenarios, ensuring generated scenes integrate properly into spec.md.

The best way to manage acceptance testing scenarios during requirement changes is to apply change auditing against existing specs. By generating REFER or MODIFY scenes from the new intent, you maintain traceability and append updates directly to spec.md.

Scenario generation requires template-driven definitions to enforce consistency and traceability within spec.md. By structuring INSERT, MODIFY, and DELETE actions through templates, the system ensures change auditing supports effective review and collaboration.