specfuse
@specfuse Organization
Public Skills
deprecate-scenario
by specfuse
"Mark an Arazzo scenario or recipe as deprecated -- sets x-version deprecation metadata (deprecatedAt, replacedBy, removalDate without bumping current), verifies the replacement exists, and warns about downstream consumers. Use when retiring a scenario or recipe in favor of a successor."
design-flow
by specfuse
"Compatibility shim -- /design-flow has been replaced by /design-scenario as part of the Arazzo integration. Use when someone asks to design a flow; redirect to scenario authoring (all procedural flow docs are now Arazzo-driven), or edit a domain overview directly for conceptual overviews."
list-scenarios
by specfuse
"Browse existing Arazzo scenarios and recipes filtered by domain, actor role, tag, or status. A discovery tool -- use when you want to understand what behavioral coverage already exists before authoring, updating, or reviewing scenarios. Pure file-system scan with YAML metadata extraction, no subagent."
impact-scenarios
by specfuse
"Determine which Arazzo scenarios and recipes are affected by a code change by cross-referencing changed operationIds, events, and schemas against the corpus. Use after renaming or removing spec artifacts, or before a PR, to find the blast radius; wraps the impact-analyzer subagent, traverses recipe extends chains, and highlights critical-path scenarios."
review-scenario
by specfuse
"Request an independent pre-merge review of an Arazzo scenario or recipe -- spawns the scenario-reviewer subagent, which evaluates the file cold (without the original PM intent) across seven quality and granularity categories and returns an APPROVE / REQUEST CHANGES / NEEDS DISCUSSION verdict. Use before merging a scenario for an unbiased second opinion."