Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/arrrrny/zuraffa/speckit-workflow)<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-workflow"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-workflow.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.03657 |
| Opus 5 | $0.00015 | $0.01828 |
| Sonnet 5 | $0.00006 | $0.00731 |
| Haiku 4.5 | $0.00003 | $0.00366 |
Grade A, and why
speckit-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Speckit Workflow (Zed) — Autonomous Mode
Run the full Specification-Driven Development lifecycle within Zed without any user interaction. This skill orchestrates the sequential execution of:
- Pre-Flight — System context & project health
/speckit-specify— Create/update the feature specification/speckit-plan— Generate the implementation plan/speckit-tasks— Generate actionable tasks/speckit-implement— Execute the implementation
No review gates. No questions. No stops. If information is missing, search the project codebase for the answer. If truly blocked, make a reasonable default decision and continue.
User Input
$ARGUMENTS
Parse the user input for the following:
Required:
- Feature description — A natural language description of what to build.
Optional (extracted from input if present):
- scope — One of
full,cli-only,generator-only,plugins-only,docs-only. Defaults tofull. - branch — An explicit branch name to use (e.g.,
--branch my-feature). If not provided, the speckit-git-feature hook auto-generates one.
If no feature description is provided, stop immediately — do not ask the user to clarify. The workflow cannot proceed without a description.
Core Rule: Never Ask, Always Search
When you encounter any ambiguity or missing information during any step:
- Search the project: Use
grep,find_path, orclaude_context_search_codeto find existing patterns in the codebase. - Read the docs: Check
docs/for architecture documentation — these contain high-level system understanding. - Check existing specs: Look at
specs/directory for similar features to understand conventions. - Check existing implementations: Look at the actual code in
lib/src/for established patterns. - Scan
AGENTS.md: Contains project-specific rules and conventions for v5. - Use prior features: Check
specs/for closely related features — their specs, plans, and tasks.md files document existing patterns. - Check
.zfa/memory: The.zfa/directory contains project memory — plans, runs, decisions, blueprints, manifests, and context.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday Changed · -13 lines f986436e76e3
- 8d ago First seen · 345 lines · 30 tokens per session scan A 29e83ccfc1d1
speckit-workflow is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 3,657 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
flutter
Use when building, structuring, testing or optimizing a Flutter app — feature-first layering, Riverpod 3 or Bloc, typed gorouter, freezed models, a dio data layer, Material 3, jank hunting, widget/golden tests. Targets Flutter 3.44 / Dart 3.12. NOT React Native (that is react-native), NOT Compose Multiplatform (that…
building-flutter-apps
Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.
fl-data-layer
Builds the data layer with Freezed DTOs, Retrofit clients, the storage-seam local data manager, and repositories wired through injectable.
fl-module-scaffold
Scaffolds a new feature module under apps/main/lib/presentation/modules using the bundled module generator.
fl-route-config
Configures routes with the IRoute / CustomRouter abstractions in core and exposes navigation via a BuildContext coordinator.
fl-ui-components
Awareness index of every reusable widget in flui, fltheme, flmedia, and core's commonwidget — name, one-line purpose, when to reach for it instead of writing a new one.