to-spec

To generate a project spec from a conversation, invoke the tool to synthesize existing context into a structured spec.md file, automatically scaffolding the necessary plan directories without requiring additional user interviews.

Creating a structured plan template from chat context involves deriving a runnable plan slug, scaffolding a directory structure, and writing a complete spec.md that captures all discussed decisions to prevent loss of planning context.

You do not need to provide a specific path or slug to scaffold a plan directory, because the system can automatically derive a slug from the conversation context or accept one if provided by the user.

You can automate documentation generation without follow-up questions, as the system enforces no user interviews and relies entirely on the existing conversation context to produce the final spec template.

The spec generation process creates a directory structure under .ai/plans/{slug}, scaffolds a tasks subdirectory, generates a learnings file, and outputs the path to the written spec.md document.

You should use automated spec generation for task planning when you need to convert ongoing planning discussions into a concrete, standardized spec template quickly, eliminating the risk of losing decisions or duplicating drafting effort.