InnovaticInnovaticDocs
Features

Documents

AI-generated artefacts that persist — specs, plans, analyses, reviews, and test plans, all searchable.

When you use Innovatic's specialized modes, the output isn't just a chat message — it's a structured document saved to your project. Specifications, implementation plans, code analysis reports, review comments, test plans — all stored, all searchable, all available the next time you open the project.

Document types

Each mode produces a specific type of document:

TypeCreated byWhat it contains
SpecificationsSpecforge modeEpic + stories, requirements, acceptance criteria
PlansPlan modeStep-by-step implementation breakdown
AnalysesAnalyze modeCode quality, security, and architecture findings
ReviewsReview modeInline code comments organized by file
Test PlansTest Plan modeManual test cases with steps and expected results

Accessing documents

The top bar shows a badge for each document type with the current count for that worktree. Click any badge to open a searchable list of all documents of that type.

From the modal you can:

  • Search across document titles
  • Filter by status or date
  • Preview document content inline
  • Open the full document
  • Delete documents you no longer need

When more than two types are active, Innovatic combines them under a single Documents button so the top bar stays clean.

Conversation history

Every conversation is saved and searchable. Access past sessions from any worktree:

  • Search by keyword, mode, or date
  • Load a previous conversation to continue where you left off
  • Full message history preserved, including all content blocks

Where documents are stored

All documents live inside .context/ within each worktree:

.context/
├── specs/       # Specforge specifications
├── plans/       # Plan mode output
├── analyses/    # Analyze mode reports
└── tmp/         # Temporary interaction files

This directory is automatically excluded from git commits — your AI artifacts stay local and never pollute your repository history.

Documents are scoped to their worktree. Each agent has its own isolated .context/ — documents from one task don't mix with another.

  • Kanban Board — push specs from Specforge directly to your task board
  • Work Modes — the modes that produce each document type

On this page

On this page