一键导入
cog-init
Use when setting up a project for cogitation for the first time, or the user says "set up cogitation", "init", or "configure this project"
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when setting up a project for cogitation for the first time, or the user says "set up cogitation", "init", or "configure this project"
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when changing cogitation project settings (test/build/lint commands, branching conventions, graphify/codex toggles), or the user says "change config", "update settings", or "set test command"
Use at the start of any conversation — establishes the cogitation workflow and requires invoking the right skill before responding, including before clarifying questions
Use for MEDIUM-sized work — new but contained behavior (one component, no architecture/data/API change) that deserves rigor without the design-doc + plan-doc ceremony of brainstorming
Use when the user wants to tailor the cogitation workflow — says "customise", "recustomise", "change the workflow", "make TDD less strict", "turn off finishing-branch", or wants a skill looser or disabled
Use when EC memories need cleanup — deduping, pruning stale entries, hygiene — or the user says "audit memories", "clean up EC", or "review what's stored"
Use before any feature work or new feature — interviews you about the feature one question at a time, pushes back on gaps, and saves a design doc with a decisions log
| name | cog-init |
| description | Use when setting up a project for cogitation for the first time, or the user says "set up cogitation", "init", or "configure this project" |
First-time setup for a project. Creates the foundation for memory-enhanced workflows.
Announce: "I'm using the init skill to set up cogitation for this project."
Verify EC → Check Existing → Scaffold → Configure → Store
Test that Engram Cogitator is running:
ec_search: test connection
If EC unavailable: Stop. Cogitation requires EC.
"EC connection failed. Please ensure engram-cogitator is running. See: https://github.com/MereWhiplash/engram-cogitator"
Search for prior initialization:
ec_search: project config
ec_search: cogitation initialized
If found: Ask before reinitializing.
{
"questions": [{
"question": "This project already has cogitation context. What would you like to do?",
"header": "Existing",
"options": [
{ "label": "Keep existing", "description": "Exit without changes" },
{ "label": "Reconfigure", "description": "Update settings, keep memories" },
{ "label": "Fresh start", "description": "Clear all and reinitialize" }
],
"multiSelect": false
}]
}
Create standard directories if they don't exist:
mkdir -p docs/designs docs/plans docs/sketches
Analyze the project to suggest defaults:
ls -la
Look for:
package.json → Node/npm/pnpm/bungo.mod → GoCargo.toml → Rustpyproject.toml / requirements.txt → PythonMakefile → Make-basedUse AskUserQuestion to confirm/customize commands:
{
"questions": [
{
"question": "What command runs your tests?",
"header": "Test",
"options": [
{ "label": "[detected]", "description": "Based on project files" },
{ "label": "pnpm test", "description": "pnpm package manager" },
{ "label": "npm test", "description": "npm package manager" },
{ "label": "go test ./...", "description": "Go testing" }
],
"multiSelect": false
},
{
"question": "What command checks types/lints?",
"header": "Lint",
"options": [
{ "label": "[detected]", "description": "Based on project files" },
{ "label": "pnpm lint", "description": "ESLint via pnpm" },
{ "label": "go vet ./...", "description": "Go vet" },
{ "label": "None", "description": "Skip linting" }
],
"multiSelect": false
},
{
"question": "What command builds the project?",
"header": "Build",
"options": [
{ "label": "[detected]", "description": "Based on project files" },
{ "label": "pnpm build", "description": "Build via pnpm" },
{ "label": "go build ./...", "description": "Go build" },
{ "label": "None", "description": "No build step" }
],
"multiSelect": false
}
]
}
{
"questions": [{
"question": "What branching convention do you use?",
"header": "Branches",
"options": [
{ "label": "feat/fix/chore", "description": "feat/<name>, fix/<name>, chore/<name>" },
{ "label": "feature/bugfix", "description": "feature/<name>, bugfix/<name>" },
{ "label": "Flat", "description": "Just descriptive names" }
],
"multiSelect": false
}]
}
Store the project configuration in EC:
ec_add:
type: config
area: project
content: |
test_command: <user choice>
lint_command: <user choice>
build_command: <user choice>
branch_convention: <user choice>
rationale: Project configuration for cogitation workflows
Mark initialization complete:
ec_add:
type: pattern
area: project
content: Cogitation initialized for this project
rationale: Marker for init detection
Workflow gate: if you write .cogitation/config.json, leave
workflow.customized unset — the first session then shows the one-time
default-profile nudge, and the silent gate handles the rest. Do not force
customization at init.
Present what was set up:
Cogitation initialized
- Test:
<command>- Lint:
<command>- Build:
<command>- Branches:
<convention>Directories created:
docs/designs/,docs/plans/Ready to use cogitation skills. Try
@brainstormingto start a feature.
Suggest next steps based on context: