wiki-add-task

Capture ad-hoc ideas, bugs, tasks, and notes into the vault. Three entry points depending on where you are:

Entry	When	What happens
`/wiki-add-task <text>`	You're in a Claude Code session (NOT Hermes compact)	Creates `raw/transcripts/YYYY-MM-DD-{type}-{slug}.md` with ad-hoc capture frontmatter
Filesystem drop	Hermes Agent compact mode (no slash commands available)	Same as above — create `.md` in `raw/transcripts/`, dev-loop discovers it
Filesystem drop	You're NOT in a Claude session (Obsidian, editor, sync)	Create any `.md` file in `raw/transcripts/` using the vault template — dev-loop discovers it on next cycle
Dev-loop discovery	Automatic, next cycle	Scans `raw/transcripts/` for new files since last cycle, surfaces as claimable work
Path Rule: Captures ALWAYS go to `$(skillwiki path)/raw/transcripts/` (Layer 1). Never under `projects/{slug}/raw/` — that violates SCHEMA.md Layer 1 immutability.

Exception: Explicit project task requests

When the user explicitly says "raise task to project X", "add a task for X", "create a feature request for X", or uses a directive structure like "raise task to {project} {description}", the intent is a work item, not a capture:

User wording	Action	Target
"capture this", "note this", "remember this"	Use wiki-add-task (this skill)	`raw/transcripts/`
"raise task to project X", "add task to X project"	Escalate to `proj-work`	`projects/{slug}/work/YYYY-MM-DD-{slug}/task.md`
"save to wiki" + content	Use `wiki-ingest`	`concepts/`, `entities/`, etc.
This is NOT a violation of the "ALWAYS" rule below — explicit project task requests are a distinct user intent that bypasses raw capture and goes directly to a Layer 3 work item.

When This Skill Activates

User invokes /wiki-add-task with a description.
User says "add task", "capture this", "note this", "remember this", "log this idea", or similar.