菜单
Manage project memories - constraints, decisions, conventions with conflict detection and resolution
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when asked to implement, build, add, fix, refactor, or change anything in a codebase — vague asks included. Tier-driven phases: intake, investigate, plan, build, verify, deliver. Entry point: /implement.
The map-reduce + blackboard pipeline that lets a small-context model digest inputs far beyond one attention window — a codebase, a long document, a corpus, a multi-part idea — and state only evidence-anchored, citation-checked conclusions. Use when / Trigger: executing or resuming an analyst run (/analyst:digest, /analyst:resume, /analyst:show), or any analysis input exceeds one 200-line chunk.
Use whenever a change needs a system-design decision — architecture, system design, data model, module/service boundaries, interface/API contracts, scale, or an ADR. The canonical discipline for designing systems: tradeoffs made explicit, the design sized to the 15 elicited context fields, one-way doors found by a five-flag checklist (one ADR each), every component earning its place through a two-cell subtraction walk, and every "start simple" seam carrying a concrete extraction trigger. Executed as checkpointed run steps (references/phase-*.md) that write into docs/architecture/ + docs/adr/ per scribe's documentation contract.
Stay focused on the project with the task in hand; recall another project's knowledge ONLY when the task actually needs it. When a task requires changing a shared dependency you own (a local composer/npm package in another repo), make the change IN that owning repo — commit, push, retag — then update and re-verify the consumer. Trigger: an edit is about to land inside a dependency directory, or a task can't be done without touching a package you maintain elsewhere.
Use when asked for a deep audit, production-readiness review, architecture review, or prioritized recommendations across a codebase or subsystem — orchestrates parallel reader agents with adversarial verification and publishes findings to docs/deep-analysis/
Run a large, multi-place task as a checkpointed state machine over the runs store — plan, adversarial plan review, wave-by-wave execution, synthesis — one step per invocation, resumable after any interruption. Trigger: cross-file refactor, data migration, large feature build, multi-source research — work that cannot finish in one pass. Manual invocation: /deep-work.
基于 SOC 职业分类
| name | taskmanager-memory |
| description | Manage project memories - constraints, decisions, conventions with conflict detection and resolution |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion |
.taskmanager/taskmanager.db holds the project-wide memory: table memories, FTS5
mirror memories_fts, task-scoped entries in state.task_memory. You dispatch; the
work lives in ONE reference file per situation. Load only the matching row.
| Situation | Load |
|---|---|
| Find memories for the current work (keywords, files, domains, task IDs); record usage | references/memory-search.md |
| Browse or inspect memories (list, show, get, statistics) | references/memory-query.md |
| Capture a new long-lived decision / constraint / convention | references/memory-create.md |
| Correct, deprecate, or supersede an existing memory | references/memory-update.md |
| Check active memories for conflicts; resolve them | references/memory-conflicts.md |
| Task-scoped memory: add / retrieve / promote | references/memory-task-scoped.md |
RULES (always):
taskmanager:init first, stop.kind: constraint, decision, bugfix,
workaround, convention, architecture, process, integration, anti-pattern, other ·
status: active, deprecated, superseded, draft · source_type: user, agent,
command, hook, other. Never invent values.deprecated or superseded (the audit trail).source_type = 'user' → never auto-modified; every change asks via AskUserQuestion.memories_fts MATCH, never LIKE over body.list --all.deferrals table (owned by the run and update
commands) — never create a memory to track a deferral..taskmanager/logs/activity.log, append-only, levels ERROR and DECISION:
<timestamp> [ERROR|DECISION] [memory] <message> — one line per create, update,
deprecate/supersede, memory-applied-to-task, conflict resolution, and error.