القائمة
RETIRED — the thoughts/ scratch-directory convention is superseded by the runs store. Trigger: any impulse to create thoughts/<task-slug>/ or to persist a multi-session board outside the database.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | thoughts |
| description | RETIRED — the thoughts/ scratch-directory convention is superseded by the runs store. Trigger: any impulse to create thoughts/<task-slug>/ or to persist a multi-session board outside the database. |
The thoughts/ convention ("the board must outlive the window") IS the runs
store now: runs + run_steps in .taskmanager/taskmanager.db, briefs and
artifacts at .taskmanager/runs/<run-id>/. One state store, no parallel file
store — docs/adr/0004-single-state-store-sqlite.md.
Old thoughts/ layer | Where it lives now |
|---|---|
scratch.md (running notes) | run_steps.notes; larger notes = a disk artifact listed in artifacts_json |
blackboard.md (fan-out board) | the wave briefs + wave-*-reports.md under .taskmanager/runs/<run-id>/ |
conclusions.md (staging to promote) | the ensemble-verified survivors → scribe capture / docs/deep-analysis/ |
| "externalize only when it won't fit" (felt) | the countable entry conditions in skills/deep-work/SKILL.md |
| adversarial membrane | the harness, skills/adversarial-verify/SKILL.md |
Do not create a thoughts/ directory. Multi-session work → start a run
(/deep-work); resume is SELECT * FROM v_next_step per
docs/architecture/runtime-state.md. An existing thoughts/ dir from older
work: drain settled items to scribe capture / docs/deep-analysis/, then
delete it.
