silver-fast

Classify development changes into Tier 1, Tier 2, or Tier 3 and route to gsd-fast, gsd-quick, or silver-feature.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill silver-fast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: silver-fast
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/silver-fast
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill silver-fast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically triages changes by complexity and routes them to the appropriate execution path, reducing manual decision-making and speeding up delivery.

Core Features & Use Cases

  • Autonomous classification of changes into Tier 1, Tier 2, or Tier 3
  • Routing to gsd-fast, gsd-quick, or silver-feature based on tier
  • Scope checks and escalation when the change grows beyond initial bounds
  • Optional deferred-item signaling for later follow-up

Quick Start

Describe your change succinctly and invoke the silver-fast skill to route the work to the correct execution engine.

Frequently Asked Questions about silver-fast

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate triage for development changes?

Automate development change triage by invoking the skill with a succinct change description to classify complexity into tiers and route work to the correct execution engine.

Can I use automated triage for large-scale architectural changes?

Automated triage for large-scale architectural changes is supported by classifying work into Tier 3 and routing it to the silver-feature execution path.

What is the best way to route multi-file feature work automatically?

Multi-file feature work routes automatically by classifying the change into Tier 2 and directing it to the gsd-quick execution path.

How do I handle scope escalation when a change grows beyond initial bounds?

Scope escalation when a change grows beyond initial bounds is handled through built-in scope checks that trigger automatic escalation paths.

Do I need external data to classify change complexity into tiers?

No external data is required to classify change complexity; the triage relies solely on the change description and defined criteria to determine scope.

Why does automated decision-making speed up delivery for trivial edits?

Automated decision-making speeds up delivery for trivial edits by classifying them as Tier 1 and routing directly to the gsd-fast execution path.