Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

refactor(aidd-refine): add the brief check and action links to the brainstorm skill

Offen
  • Stimmt etwas nicht?
#1,084 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
64/100
Issue-Typ
Refactoring
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
markdown, typescript
Bereich
developer-experience, tooling

Rechercherichtung

Read the lean plan skill from #1080 and its validate-plan.cjs, then inspect aidd-refine:01-brainstorm and the tests under scripts/__tests__/. Write the mutation tests first, including Windows line endings, and run them to confirm they fail. Done means the persisted brief is checked only on the conclude persist branch, the action links are added without creating a loop, the pre-commit gates pass, and the two named models still produce the brief in the cited scenarios.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Problem

aidd-refine:01-brainstorm was leaned in #1072 without two things the lean plan skill (#1080) has: a bundled check of the file it writes, and a markdown link from each action to the next. On mistral-medium-2604 a plain "go to the next action" let the model stop to ask whether to continue, and a link to the next action file removed that stop on the plan skill (4 of 4 plans written, against 2 of 3 without it).

Scope
  • A markdown link at the end of capture to explore and of explore to conclude. No link back from a later action to an earlier one: on the plan skill a link back made the model loop between the two (30 judge calls on one run).
  • A bundled script that checks the persisted brief against assets/discovery-brief.md (sections, Clear / Assumed / Open, status: approved, no comment or {{...}} left). It runs only when the user chose to persist the brief: conclude calls it on that branch and nowhere else.
  • A test under scripts/__tests__/ with one mutation per rule, written first and seen failing, covering Windows line endings.
Acceptance criteria
  • The pre-commit gates pass.
  • A persisted brief that breaks a rule is reported by the script, and no brief means no script run.
  • Claude haiku and mistral-medium-2604 still hold the brainstorm loop and produce the brief on "stop", on the scenarios used for #1072.
Prior art in this repo
  • #1071 and #1072 (the lean brainstorm), #1075 and #1080 (the lean plan skill, its validate-plan.cjs and its links).
Out of scope
  • plan, implement, assert, review.
  • A script for a brief that was never persisted.
Vorherrschende Sprache
TypeScript
Sterne
481
Forks
45
Ø Merge
1 T. 2 Std.
Gemergte PRs (30 T.)
77

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ai-driven-dev/framework

Alle Issues in ai-driven-dev/framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.