菜单
Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "engineer plugin -> discuss skill", "engineer plugin -> discuss skill <slug>", "I have an idea about", "should we build", "let's think about".
用 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 | discuss |
| description | Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "engineer plugin -> discuss skill", "engineer plugin -> discuss skill <slug>", "I have an idea about", "should we build", "let's think about". |
The upstream funnel of DAE — a divergent brainstorm (forked from superpowers:brainstorming) that ends in one of three outcomes: drop, park, or promote. Most ideas die here; some park as features/NNN-slug/ with status: parked; survivors promote to status: ready.
engineer plugin -> discuss skill, no argument. New exploration.engineer plugin -> discuss skill <slug>. Resume a parked feature.Not for: feature-work prep on an already-Ready feature (prime-context), or editing a committed feature (feature-edit).
${PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md). Load CHARTER.md and the last ~20 lines of .engineer/discussions.log. With a slug arg: also load that feature's feature.md + prior handoffs/*-discuss.md; reject if its status is ready/in-progress (→ feature-edit) or done..engineer/discussions.log: <ISO-timestamp> | <slug> | dropped | <one-line why>. Draft the "why" from context; user confirms/edits.feature-init with feature_intake { status: parked, autonomy_level: null, ... }.autonomy_level (low/medium/high, charter caps surfaced); if the user can't decide, fall back to park. Then invoke feature-init with status: ready.<timestamp>-discuss.md handoff into the new feature folder. For drop, the log line is the record — no handoff.Continuing a parked feature: each session appends a new discuss handoff; feature.md is refined in place. Promoting a continued feature flips status to ready directly — feature-init is not re-invoked.
For park/promote, emit per ${PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null. Drop emits no handoff.
feature-init (invoked for park/promote).