菜单
Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "/engineer.prime-context", "prime context", "load context before we start", "get up to speed on feature X".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | prime-context |
| description | Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "/engineer.prime-context", "prime context", "load context before we start", "get up to speed on feature X". |
Load working memory before pipeline work on a Ready feature — the convergent counterpart to discuss. Forked from superpowers:brainstorming but inverted: no exploration, just loading and orienting. Produces no artifact.
A prep step (not a checkpoint) between feature-init and discover-acs, on any feature the agent hasn't already worked this session.
Skip when: the agent just created the feature this session (context already warm). Not for: exploring whether a feature is worth doing (discuss).
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md); locate the feature (slug arg or branch name). Reject if no folder / no feature.md.feature.md, CHARTER.md, manifest.yml, prior handoffs/ (especially the originating *-discuss.md), and the files named in feature.md's "Related code / design pointers". When loading those code pointers, prefer LSP — documentSymbol for file shape, hover for signatures/types, workspaceSymbol to pull in the symbols they reference — over reading whole files blind, when an LSP MCP capability is available; fall back to grep + Read otherwise. See ${CLAUDE_PLUGIN_ROOT}/references/code-lookup.md.feature.md. Then stop — prime-context orients, it does not interview.Re-invocation re-loads fresh (no incremental diffing).
Emit per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; artifacts: []; human_action_needed: no; recommended_next: "/engineer.discover-acs".
Always emit a breadcrumb. Earlier versions produced no handoff because prime-context creates no artifact. Users expect a breadcrumb after every skill invocation (distbute Jun 4: "emit the handoff") — surprising them with "no artifact by design" breaks the agentic-summary contract. The breadcrumb records: which feature was primed, what files were loaded, any new pointer added to feature.md, and the next recommended skill. Body can be one paragraph — frontmatter is the load-bearing part for progress-log propagation.
Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss", "/engineer.discuss <slug>", "I have an idea about", "should we build", "let's think about".
Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers — "/engineer.feature-init", "create a feature", "start a new feature", "init a feature".
Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project. Triggers — "/engineer.next", "what's next", "what should I work on", "what should I do next", "where do I pick up".
Use to bring a project into the DAE methodology, or to check an onboarded project for gaps. Triggers — "/engineer.onboard", "onboard this project", "set up DAE here", "adopt the methodology", or when a DAE skill fails because no manifest exists.
Use to propagate DAE state — turning handoff summaries into visible progress. Triggers — "/engineer.progress-log", "sync progress", "update the tracker", "reconcile the tracker", "refresh feature status".
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".