菜单
Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "engineer plugin -> prime-context skill", "prime context", "load context before we start", "get up to speed on feature X".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Analyze changed code for complex, under-tested functions using CRAP scoring; produce ranked refactor and test recommendations.
Validate strict DAE quality gates after implementation-affecting changes, require machine-readable evidence, and write the quality-gate summary before completion or release.
This skill should be used when the user asks to "run mutation testing", "mutate my code", "kill mutants", "check test quality", "find surviving mutants", "verify test effectiveness with mutations", "run stryker", "run mutmut", "run pitest", "set up mutation testing", "how good are my tests", "are my tests catching bugs", or mentions mutation testing, mutation score, or mutant survival in the context of testing. It adds a third validation layer to the ATDD workflow: after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies that tests actually catch bugs.
This skill should be used when the user asks to "build a feature", "implement a feature", "add functionality", "start development", "write acceptance tests", "write specs", "use ATDD", "use TDD with acceptance tests", or begins any feature implementation work. Also available as the atdd plugin's main skill. Enforces the Acceptance Test Driven Development workflow: write Given/When/Then specs before code, generate a project-specific test pipeline, and maintain two test streams.
This skill should be used when the user asks to "build a feature with a team", "use ATDD with agents", "create an ATDD team", "set up a team for ATDD", "orchestrate agents for ATDD", "use team-based development", "coordinate agents for feature development", "run the ATDD workflow with teammates", "add ATDD to my team", "extend my team with ATDD", "join the team with ATDD agents", "add spec-writer and reviewer to the team", or "add ATDD roles to the existing team". It orchestrates a six-phase ATDD workflow — spec writing, spec review, pipeline generation, implementation, refine, verify & harden — spawning a fresh agent per phase so no agent erodes across a long-running feature.
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
| name | prime-context |
| description | Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "engineer plugin -> prime-context skill", "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).
${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".feature.md. Then stop — prime-context orients, it does not interview.Re-invocation re-loads fresh (no incremental diffing).
Emit per ${PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; artifacts: []; human_action_needed: no; recommended_next: "engineer plugin -> discover-acs skill".