specfuse
@specfuse Organization
Public Skills
ideation-groom
by specfuse
"Periodically triage the whole initiative ideation backlog -- surfacing ideas whose specs are authored and awaiting a mint decision, parking stale ones, and flagging internal dupes, items overtaken by minted work, under-shaped entries, bundle drift, and orphaned dossiers. The backlog analog of the PM's roadmap-sync: report-first, read-mostly (orchestrator registries/roadmap read-only), writing only the backlog index and never deleting a row or dossier."
ideation-capture
by specfuse
"Capture a candidate initiative into the ideation backlog -- one index row plus a stub dossier under docs/product/backlog/, both at state idea. Accepts a typed title or --from-issue <url>, the intake path for ideas submitted by people outside a kit-configured project. The frictionless pre-intake entry point that records an idea so it is never lost. Use before any INIT- is minted; deliberately low-ceremony with no interrogation, no readiness assessment, and no orchestrator-repo write."
ideation-publish
by specfuse
"Publish a shaped backlog idea to GitHub as an issue, so it can be assigned to people and planned on a GitHub Project while its specs are authored. Explicit and opt-in per idea -- offered at the ready transition, never performed by it. Mirrors state silently afterwards; confirms anything that adds new public prose."
prepare-handoff
by specfuse
"Produce a feature handoff manifest under api/docs/handoffs/ per the orchestrator's consumer contract -- runs the full validation suite, regenerates scenario docs and bundles, builds operation/async/entity/scenario inventories and the prompt index, then delegates manifest composition to the handoff-composer subagent. Use when packaging a completed spec feature for downstream implementation. Produces one artifact in this repository and writes nothing outside it: the orchestration repo creates its registry entry and mints the INIT- on receipt."
initiative-intake
by specfuse
"Create a new initiative's registry entry in the orchestration repo, mint its INIT-YYYY-NNNN correlation ID, emit the initiative_created event, and set state to drafting. The entry point for every initiative's lifecycle -- no downstream skill (drafting, validation, planning) can operate until a valid registry entry exists. Use when a human starts a new initiative (renamed from feature-intake in the Model-B reframe)."
ideation-shape
by specfuse
"Interactively shape a captured backlog idea until its specs can be authored: fill its dossier, drive a four-point readiness checklist, and move it idea → shaping → ready, recording any decision to bundle several ideas into one initiative. Use between ideation-capture and spec authoring; evidence-led (infer from files first, ask last), ends at ready, offers to publish the idea to GitHub, and does not mint the INIT-."
design-scenario
by specfuse
"Interactively design a new Arazzo scenario from PM intent through a structured 11-step flow (intent, domain, inventory scan, actors, step walk, failure modes, UI hints, generate, validate, Mermaid sanity check, write). Use when authoring a new behavioral scenario; delegates generation and validation to the scenario-architect and scenario-validator subagents."
update-scenario
by specfuse
"Apply targeted, surgical edits to an existing Arazzo scenario -- operationId or event renames, step add/remove, actor changes, extension updates, version bumps, deprecation -- then re-validate. Use when modifying an existing scenario rather than creating one; can auto-detect renames from recent git history and guides version-bump decisions."
spec-validation
by specfuse
"Invoke Specfuse validation on drafted specs, interpret the output into actionable failure feedback (via a common-error interpretation table), and own the drafting → validating → planning state transitions that hand the initiative to the PM agent. Use when the human requests validation during or after a drafting session; emits spec_validated and feature_state_changed events with idempotence guards, and never self-validates, fixes specs, or transitions on a failed run."
spec-issue-triage
by specfuse
"Triage spec issues raised by downstream agents (GitHub issues labelled specfuse:spec-issue) -- deciding, via a four-case decision tree, whether the fix belongs in /product/ (a spec-content correction the specs agent makes and re-validates) or in the generator project (a template issue to file), then resolving or routing accordingly. The specs agent's monitor-driven skill; reads the upstream spec to distinguish a genuine template bug from a spec error propagated through generation, and escalates ambiguous cases rather than guessing."
spec-drafting
by specfuse
"Conversational three-phase guidance (feature scoping → spec drafting → pre-validation review) for drafting an initiative's OpenAPI/AsyncAPI/Arazzo specifications collaboratively with the human under /product/, keeping the human's product judgment primary while ensuring acceptance criteria are concrete, single-behavior, and QA-consumable. Use during the drafting state, after initiative intake and before spec validation; never runs the validator, modifies frontmatter, or writes test plans."
create-job
by specfuse
"Create a scheduled job (run-* operation) -- a cron-triggered thin fan-out dispatcher that queries the database and publishes one event per work item for independent per-item processing with retry and DLQ isolation. Use when adding a cron-driven background job to the v2 async architecture; enforces the AsyncAPI handbook's fan-out pattern, message and operation shapes, and validation."
design-async
by specfuse
"Design or add async specifications (events, scheduled jobs, handlers) for a domain in the v2 pub-sub architecture. Use when modeling an event-driven flow -- API-triggered events, fan-out jobs, or workers; enforces the AsyncAPI handbook's three allowed patterns, message/snapshot/operation shapes, x-emits cross-links, and full validation."
validate-scenarios
by specfuse
"Run the complete validation suite for all Arazzo scenarios and recipes -- Spectral lint plus structural and cross-spec checks (operationId and event resolution, recipe chains, granularity). The Arazzo equivalent of /validate and /validate-async; use to verify scenarios before merge or generation."
validate
by specfuse
"Run the complete validation suite for the project's OpenAPI specifications -- bundle, file structure, OpenAPI Generator, SpecFuse validator, Spectral lint, and Redocly -- plus AsyncAPI validation if async specs exist. Use to verify specs are correct and ready for code generation."
validate-async
by specfuse
"Run the complete validation suite for the project's AsyncAPI specifications -- bundle, structural validation, and Spectral lint -- stopping on errors. Use to verify async specs are correct and ready for code generation."
bump-generator-pin
by specfuse
Kit-side half of a generator release — pin a newly published generator jar into generator.lock, then walk the maintainer through the kit version bump, compatibility.md row, and PyPi publish. Trigger when a new generator version has been released to Specfuse/generator-dist and you have its version + SHA-256. Maintainer-only (not copied into client projects).
preview-async
by specfuse
"Launch the AsyncAPI documentation preview server (port 8082) in the background for live viewing of the async specs while editing. Use when you want to visually review AsyncAPI docs in the browser; coexists with the OpenAPI preview on 8081."
bundle
by specfuse
"Bundle the OpenAPI and (if present) AsyncAPI specifications into single self-contained files for code generation. Use when you need a bundled spec artifact before generating code, or when a downstream validator or generator requires the combined output."
file-generator-issue
by specfuse
"File a GitHub issue against the Specfuse generator repo for a code-generation bug, then start a background monitor that polls for resolution and auto-verifies the fix when the generator agent resolves it. Use when generated code is wrong and you need to report the symptom (never propose template fixes) and resume work once fixed; supports a --verify-only mode."
generate
by specfuse
"Generate frontend (Flutter) and backend (C#) code, workers, and Markdown documentation artifacts from the API specifications. Use when you want to produce generated code and docs from validated specs; runs the project generate scripts and reports each step's outcome."
design-recipe
by specfuse
"Design a new Arazzo setup recipe that provisions test fixtures via real OpenAPI operations so scenarios start from a known state. Use when a scenario needs precondition entities no existing recipe provides; walks composition (extends chains, depth limits, output contracts, $system actor) and validates with zero forbidden extensions."
preview
by specfuse
"Launch the Redocly documentation preview server (port 8081) in the background with live reload for viewing the OpenAPI specs while editing. Use when you want to visually review the API docs in the browser as spec files change."
create-worker
by specfuse
"Create an event-handler worker (on-* operation) that subscribes to an existing or new domain event and does the work directly, optionally AI-powered and optionally emitting completion events. Use when adding an async subscriber to the v2 pub-sub architecture; enforces AsyncAPI handbook rules, snapshot payloads, x-subscription/x-emits wiring, and validation."