From cothought
Captures project ideas, performs web research with subagent, creates zettelkasten-style research notes, links into projects.md. Use for exploring ideas before repo creation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cothought:projectThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Capture a project idea, research it, and create a proper project note linked into the network. This skill is for the *thinking and documenting* phase — exploring what a project could be, gathering research, and writing it up. It does NOT create repos, folders, or code. When the user is ready to start building, they use `/cothought:begin-project`.
Capture a project idea, research it, and create a proper project note linked into the network. This skill is for the thinking and documenting phase — exploring what a project could be, gathering research, and writing it up. It does NOT create repos, folders, or code. When the user is ready to start building, they use /cothought:begin-project.
Today's date: !date +%m-%d-%Y
Load config: Read ~/.claude/cothought.json. If it doesn't exist, tell the user to run /cothought:setup first and stop. Extract notes_dir.
Notes directory: <notes_dir from config>
skills/zettelkasten/skill.md) for note format conventions, linking rules, and history table requirements.projects.md in the notes directory to see existing projects.Understand the idea. Ask the user what they're thinking, or infer from context. Get enough to know what to research.
Research. Spawn a research subagent (Task tool, subagent_type: general-purpose, run_in_background: true) to search the web for:
run_in_background: true) so the conversation keeps flowing. Check the output later and weave findings into the note.Search the note network. Glob and Grep the notes directory for existing notes related to this project idea — concept notes, journal entries, other project notes. Read anything relevant for context.
Create the project note. Follow zettelkasten note conventions from the zettelkasten skill:
ai writing quality.md)---, history table belowLink it in projects.md. Add the project to the appropriate section (Active, Research/Background, Dormant) using standard markdown link format: [project name](project%20name.md) with a short description.
Back-link. If the project note references other existing notes, add back-links to those notes.
Report back. Tell the user the note is created, what research was found, and what it connects to. If they want to spin up a repo, point them to /cothought:begin-project.
projects.md is the index only — no project ideas inline.[title](file%20name.md)), not wikilinks. Validate with Glob before writing.npx claudepluginhub elliotbonneville/claude-cothought --plugin cothoughtCaptures a single user-voiced idea into a provenance-tracked folder in an ideas repo, with optional GitHub issue mirror. For recording one idea at a time, not bulk extraction.
Manages a vault-first, project-scoped Obsidian research knowledge base: bootstrap, note routing, hub/plan/index maintenance, registry updates, lifecycle actions, and lint orchestration.
Creates or updates PARA project notes in an Obsidian vault with structured fields (outcome, deadline, status, next action).