Verify implemented behavioral branches against epic specs from .flux and git diff.
npx skills add https://github.com/Nairon-AI/flux --skill flux-grill
Please help me install this Agent Skill. Skill: flux-grill Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-grill Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-grill
After an epic is implemented, teams need a rigorous way to ensure that all behavioral branches align with the intended design and to surface edge-case gaps before shipping.
Invoke Grill after completing an epic review to exhaustively verify behavior alignment and readiness for production.
High-intent search queries and answers about installing and using this skill.
To verify behavioral branches after an epic, analyze epic intent and implemented git diffs to confirm actual behavior matches the original design specs. This process maps expected behaviors into a decision-tree and iterates branch-by-branch against the codebase to flag ambiguities.
Behavioral verification for state transitions is the process of exhaustively testing user actions, permissions, and integrations against epic specs. It builds a decision-tree model from task data to ensure actual codebase behavior aligns with the intended design before shipping.
Run an edge-case gauntlet by iterating branch-by-branch against the codebase to test empty states, concurrency, permissions, and failure modes. This generates a Behavioral Summary for risk assessment, surfacing gaps between implemented changes and epic specs.
Yes, behavioral verification works directly with git diffs and task data. It accesses epic specs stored in the .flux directory and fluxctl-managed task data to drive a branch-by-branch verification workflow across all state transitions.
Use behavioral verification for quality assurance immediately after an epic review or right before shipping. It is needed when you must exhaustively confirm that implemented changes and state transitions align with the original epic design and surface edge-case gaps.
The best way to update epic specs when gaps are discovered is to use verification guidance that flags ambiguities for clarification. This process provides actionable steps to update specs, create new tasks, and optionally record decisions in the brain vault.
Nairon-AITrigger plan-sync to update downstream task specs after code drift.
hoavdcRecord and track organizational decisions using the RAPID framework.
robzolkosCompare the working branch with master and read modified specs.
i3ringitAnalyze specifications to map user flows, edge cases, and gaps.
