flow-next-capture

To convert a conversation into an epic spec, this Skill synthesizes your current chat into a Flow-Next spec file using source-tagged, per-line evidence, preserving exact user quotes and agent inferences.

Creating an epic spec from a live conversation requires a mandatory read-back phase before writing the file, ensuring all user quotes and paraphrases are verified and context is accurately preserved at .flow/specs/<epic-id>.md.

Yes, the epic spec capture process supports automated duplicate detection alongside memory context referencing, operating in both interactive and autofix modes to handle overlapping content during synthesis.

You can use autofix mode to rewrite compacted conversations by enabling the optional --rewrite and --from-compacted-ok controls, allowing automated handling of memory context hits and duplicates during spec generation.

A key limitation of automated conversation capture is the strict mandatory read-back requirement prior to writing, meaning the synthesis process cannot skip user verification even when running in autofix mode.

After generating a Flow-Next epic spec, you should follow the generated next-step footer guidance, which directs you to tactical planning and detailed interviewing using /flow-next:plan and /flow-next:interview.