Phase guidance for the neuroflow /output command. Orients agent approach for outputting project memory or the whole project safely and with correct exclusions.
From neuroflownpx claudepluginhub stanislavjiricek/neuroflow --plugin neuroflowThis skill uses the workspace's default tool permissions.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Enforces strict TDD workflow: Red (failing test), Green (minimal code), Refactor for features, bugfixes, refactors. Includes examples and verification steps.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
The /output command packages and moves project data out of the workspace. Its job is to give the user a clean, portable snapshot without accidentally including sensitive files.
sessions/ (local-only, can be large) and integrations.json (API credentials — must never be shared)zipfile module first; fall back to system zip/tar only if Python is unavailable.neuroflow/ state during export — the command is read-only except for writing the export log| Scope | Best for |
|---|---|
Project memory (.neuroflow/ minus exclusions) | Sharing context with a collaborator who has their own codebase; supervision meetings; archiving project decisions and reasoning |
Whole project (git-tracked + .neuroflow/) | Full handoff, long-term archiving, submitting to a data repository |
| Single phase | Focused handoff — e.g. sending only the data-analyze/ memory to a statistician |
| Excluded | Reason |
|---|---|
.neuroflow/sessions/ | Local-only operation log — large, personal, not meaningful to external recipients |
.neuroflow/integrations.json | API credentials (PubMed email, Miro token) — must never leave the local machine |
If the user explicitly asks to include sessions or credentials, explain why that is inadvisable and confirm they still want to before proceeding.
Default names for export outputs:
output-[project-slug]-[YYYY-MM-DD].zip
output-[project-slug]-[YYYY-MM-DD]/ (folder copy)
output-[phase]-[project-slug]-[YYYY-MM-DD].zip (single-phase)
Where project-slug is the project name from project_config.md, lowercased with spaces replaced by hyphens.
paper/ exists, offer to run /write-report to generate a summary first, then include it in the export alongside any manuscript files from the paper output path/write-report first to generate a summary, then include it in the export.neuroflow/reasoning/ is included in the memory export and contains all documented decisionsDo not suggest Notion or other cloud integrations — they are not implemented yet.
neuroflow:neuroflow-core — read first; defines the command lifecycle and .neuroflow/ write rulesneuroflow:notebooklm — when the user wants a podcast, infographic, slide deck, or audio summary generated from exported project materials, invoke the notebooklm skill to create a NotebookLM notebook and feed the exported files into it as sources