A grounded spec for your next software change.
Turns consequential software design decisions into validated project specifications through evidence-grounded dialogue.
When to use it
Use when the user requests a specification or design, or when design work involves triggers such as authentication, irreversible effects, concurrency, contracts, destructive operations, or cross-module dependencies.
Give it a software design problem in your project; it works through consequential choices with you and saves a validated specification.
What you provide
Uses Python 3 to run the bundled taste-test and artifact-path commands during specification validation and saving.
Optionally enables wiki grounding; when unavailable, the skill records its absence and proceeds using code evidence.
Delegates deep external research to /briesearch through a researcher; external validation also permits documentation fallbacks, so installation is not established as required.
This skill
hallouminate
Saves decisions to your wiki