Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

feat(aidd-refine): adversarial and advisory agents

未关闭
#588 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start with plugins/aidd-refine/skills/02-challenge/SKILL.md, plugins/aidd-dev/agents/checker.md and executor.md, and docs/ARCHITECTURE.md. Trace the existing install/translate pipeline and its unit fixtures, then add the two agent sources and thin actions. Done means CI covers translation, reports enforce severity caps and floors, agents remain read-only, and README explains when to use each approach.

由索引模型根据 Issue 内容生成。

描述

Problem

Refine exposes in-session recipes (challenge) but not isolated adversarial (attack assumptions, vacuous acceptance criteria, bypasses) and advisory (strengthen, prioritize) agents. Spec/plan stress-testing and constructive second opinions are improvised or skipped. The checker review path is a different job.

Scope

  • Agents adversarial and advisory under aidd-refine/agents/ (canonical source format).
  • Multi-tool presence = existing install/translate pipeline only (materialize into each installed tool’s native agent paths and formats). No symlinks across tool trees. Hosts never need to read .aidd/ for discovery.
  • Thin skill/actions to run each agent on a named artifact (spec, plan, brief) with a fixed report shape.
  • Severity floor + max findings (cap noise before any later specialist wiring).
  • Read-only; never implement; never invoke orchestrator skills.
  • Document when to use challenge vs adversarial vs advisory.

Standalone value: Spec/plan stress-test and second opinion without waiting for pluggable specialists.

Acceptance criteria

  • Both agent source files ship in the plugin.
  • Translator/unit fixture: canonical agent → at least one non-source target format (or identity when same format) — CI-able, not “UI discoverable”.
  • Adversarial: findings with severity; no writes; respects cap/floor.
  • Advisory: ordered recommendations; no writes; does not alone set a ship-blocking verdict.
  • README: challenge vs adversarial vs advisory.
  • Agents do not implement fixes or invoke orchestrator skills.

Prior art in this repo

  • plugins/aidd-refine/skills/02-challenge/SKILL.md — in-session challenge recipe (not isolated agents)
  • plugins/aidd-dev/agents/checker.md, plugins/aidd-dev/agents/executor.md — existing agent split (judge vs build)
  • docs/ARCHITECTURE.md (~L157–160) — agents invoke recipes; cross-plugin by capability
  • #548 — plan drift / challenge + acceptance-criteria gaps (user report)

Relations

Intended graph (same fields as GitHub parent / blocked-by / blocks). Formal GraphQL edges need maintainer write — see comment on #584.

Field Value
parent #584
blocked-by
blocks #591
related #548
MVP 2

Out of scope

  • Auto-wiring into every review (pluggable specialists child)
  • Project-local agents under .aidd/agents (materialize child)
  • Symlink-based multi-tool layout
主要语言
TypeScript
星标
481
派生
45
平均合并
19 小时 38 分钟
30 天内合并 PR
108

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ai-driven-dev/framework 的其他 Issue

查看 ai-driven-dev/framework 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。