deftai

deft-directive-issue-eval

Thin router for Stage A issue evaluation: isolated origin/master validity, parent WIP census, named gitignored sink. Use when the operator asks to evaluate issues, run issue-eval, or triage:evaluate. Do NOT trigger on ordinary implement, build, swarm, or design-critique dispatch.

deftai 31 14 Updated 2w ago
GitHub

Install

npx skillscat add deftai/directive/deft-directive-issue-eval

Install via the SkillsCat registry.

SKILL.md

Issue Eval

Thin router into the issue-eval contract. Operator runs task triage:evaluate.

Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.

When to Use

  • Operator asks to evaluate issues, run issue-eval, or triage:evaluate
  • ⊗ Ordinary implement, build, swarm, or design-critique dispatch

Stops

Normative rules live in `contracts/issue-eval.md`.

  1. Split read sources
  2. Verdict sink
  3. Evaluator worktrees
  4. Value advice grammar
  5. No GitHub writes
  6. Fan-out

⊗ Emit design-critique: warranted | not warranted, because from evaluation.
⊗ Reuse swarm:launch until #3649.
⊗ Write xbrief/proposed/ or GitHub from this skill.

EXIT

deft-directive-issue-eval complete -- exiting skill. Next: run task triage:evaluate, then decide with existing triage:* verbs.