Slash Command

/active-ingest

From research

Deep active-project wiki ingestion for source-grounded research corpora

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/research:active-ingest <source-path-or-topic> [--project foo] [--update-existing] [--merge-prior]

Model invocable

No pre-commands

Tool Access

This command is limited to the following tools:

BashReadWriteWebFetch

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

Run the active-project research ingestion workflow when sources need to become durable project wiki memory.

Use `skills/research/references/active-project-ingestion.md` as the controlling reference. This command is for source-dense, decision-relevant project ingestion where chronology, contradictions, assumptions, concepts, and wiki update recommendations need to survive future retrieval.

**Workflow**

1. Inventory the provided source path or topic and identify source type, date, scope, methodology, status, and confidence.
2. Extract each source before synthesis. Preserve claims, metrics,...

Command Content

24 lines · ~423 tokens

Stats

LanguagePython

Stars0

MaintenanceExcellent

Last CommitJun 11, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

Actions

Tags

Run the active-project research ingestion workflow when sources need to become durable project wiki memory.

Use skills/research/references/active-project-ingestion.md as the controlling reference. This command is for source-dense, decision-relevant project ingestion where chronology, contradictions, assumptions, concepts, and wiki update recommendations need to survive future retrieval.

Workflow

Inventory the provided source path or topic and identify source type, date, scope, methodology, status, and confidence.
Extract each source before synthesis. Preserve claims, metrics, assumptions, risks, stakeholders, decisions, and open questions with source locations.
Cluster repeated observations into themes only after document-level extraction.
Build theme evolution, concept maps, contradictions, project implications, wiki entry recommendations, and a decision support brief.
Persist durable outputs through the normal /research:save flow as separate entries when useful. Do not save one giant package unless the user explicitly asks for that.

Persistence rule

Project-specific saved entries should include projects: [<project>], workflow: collection or workflow: synthesis, source-backed Notes, and Raw excerpts sufficient for future verification.

If the request is only bulk markdown import, use /research:ingest instead. If the request is only parking files for later review, use /research:ingest --inbox.