القائمة
Use when brownfield or long-running repo work lacks durable context about architecture, conventions, or recurring gotchas that future tasks will need again.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when routed repo work still has meaningful ambiguity about behavior, constraints, taste, or acceptance intent, and that ambiguity would make planning or execution unsafe.
Use when a new request might involve repo work, tracked changes, workspace-specific decisions, or durable coordination and you must decide whether Superplan should engage before exploring or implementing.
Use when tracked work is already shaped and the next move is to execute, verify, block, or request feedback without replanning from scratch.
Use when the target is understood but the work still needs an execution path, task breakdown, or proof strategy before implementation begins.
Use when Superplan may engage and you need to decide whether to stay lightweight, create one tracked task, gather context first, or shape deeper structure before execution begins.
Use when Superplan has decided to engage and the work still needs plans, specs, proof paths, or multiple tracked tasks shaped before bounded execution can start.
استنادا إلى تصنيف SOC المهني
| name | superplan-context |
| description | Use when brownfield or long-running repo work lacks durable context about architecture, conventions, or recurring gotchas that future tasks will need again. |
Create or update durable workspace context that should persist beyond the current task.
This skill owns Superplan's durable context layer, not active task state.
Use when:
Do not run when:
Inputs:
.superplan/context/ if presentAssumptions:
Keep these layers distinct:
Use .superplan/context/README.md as the entrypoint and .superplan/context/INDEX.md as the routing layer into deeper context docs.
See references/context-indexing.md and references/durable-context-rules.md.
superplan context doc set <doc-slug> --stdin --json to write context docssuperplan context log add --kind <decision|gotcha> --content "..." --json to append workspace logs.superplan/ directly when a CLI command can own the writeUse .superplan/decisions.md only when a context update materially changes how future shaping or execution should reason about the repo.
Do not log routine indexing or summary updates there.
Use .superplan/gotchas.md for recurring context traps, misleading repo layouts, stale-doc pitfalls, or indexing failures likely to waste time again.
See references/gotchas.md.
Expected output categories:
When changed, output should say what durable truth was added or revised.
Likely handoffs:
superplan-routesuperplan-shapesuperplan context bootstrap --jsonsuperplan context status --jsonsuperplan context doc set <doc-slug> --stdin --jsonsuperplan context log add --kind <decision|gotcha> --content "..." --jsonUse the command surface that exists today instead of editing .superplan/context/, decisions.md, or gotchas.md by hand. It is faster and it keeps placement correct.
Should trigger:
Should stay out: