Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

feat(aidd-refine): adversarial and advisory agents

オープン
#588 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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
平均マージ
14時間 35分
マージ済み PR(30日)
66

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ai-driven-dev/framework のほかの issue

ai-driven-dev/framework の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。