refactor(aidd-refine): rebuild brainstorm as a deep conversational prober#298
Merged
Conversation
…ober Reformat the brainstorm skill to the skill contract (R1-R11, action anatomy, singular Input/Output, no frozen blocks) and rebuild its behavior around deep, thread-following questioning instead of a fixed checklist. The skill now follows the threads each answer opens, especially forks where two materially different builds are still possible, at the user's own altitude (functional or technical). It surfaces a leaning with its tradeoff when the facts point one way, challenges assumptions and walks limit cases as they appear, and keeps going until the idea is clear or the user is satisfied, with no fixed round count. Four actions: capture (restate + read altitude), probe (pointed questions on the live thread), integrate (fold in + judge ambiguity), finalize (consolidate + flag open assumptions + point to the fitting next move + offer to persist). References reduced to a single lean probing guide plus a topical prompt bank. finalize stays tool-agnostic (never writes a plugin:skill identifier) and persists a file to the dated path aidd_docs/brainstorm/<date>-<slug>.md mirroring the plans convention. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 What & why
aidd-refine:01-brainstormread mechanically and stopped shallow. This rebuilds it into a deep, thread-following prober and reformats it to the skill contract.🛠️ How it works
The prior version cycled a fixed dimension scoreboard with a coverage table and a 4-round cap: breadth, light touches, capped digging. An A/B against the original (same prompt and answers) showed the original went deeper by following the thread each answer opens. So the rebuild drops the machinery and keeps the depth:
probepulls the live fork (where two materially different builds are still possible), at the user's altitude. No round cap, stops when the idea is clear or the user is satisfied.finalizesurfaces a leaning with its tradeoff, flags open assumptions honestly, stays tool-agnostic (never writes aplugin:skillid), and persists a dated file ataidd_docs/brainstorm/<yyyy_mm_dd>-<slug>.mdmirroring the plans convention. See 04-finalize.md.🧪 How to verify
aidd-refine:01-brainstormon a vague idea (e.g. "add search to my app"). It should name the fork (filename vs full-text), ask pointed follow-ups, and end with a refined idea plus flagged assumptions, no coverage table.-pterse runs occasionally write the persist file to the wrong path; real interactive sessions land it at the dated path correctly.✅ I certify