flow-next-export-context

Export repository context to a markdown file for external LLM review by running the export-context workflow, which gathers repository metadata, diffs, and plan details into a consolidated document. This output is ready to share with models like ChatGPT or Claude.

You can export both plan details and implementation diffs from your repo using the plan and impl workflows. The plan export targets specific epic IDs, while the implementation export captures current branch changes for external validation.

Exporting RepoPrompt context requires FlowCTL and repository context to function. The scripted workflow depends on FlowCTL to gather content, set up prompts, and generate the final consolidated markdown file for external models.

The best way to prepare codebase changes for critique by an external AI model is building a cohesive RepoPrompt context. This consolidates metadata and diffs into a single markdown document, providing comprehensive external review of your repository.

External LLM reviews often fail with raw diffs because they lack repository metadata and plan context. Exporting a consolidated markdown file with full RepoPrompt context provides the necessary structure for models like Claude to validate code accurately.

Generate a plan export when you need to review epic-level architecture and strategy, and use an implementation export to review current branch code changes. Both workflows produce markdown files tailored for external LLM critique and validation.