Plain GSD gives agents a strong planning and execution engine. Silver Bullet is the Agentic Process Orchestrator (APO) around it: the operating layer teams need when work must be routed, reviewed, traced, documented, verified, and safely shipped.
Silver Bullet does not replace GSD. GSD helps an agent do the work well; Silver Bullet helps ensure the whole delivery path happens before code, PRs, deploys, or releases move forward.
GSD owns the core project lifecycle: .planning/ artifacts, roadmap and phase management, requirements, discussion, planning, wave-based execution, verification, review, shipping, and milestone completion.
Silver Bullet wraps GSD with task-shaped routing, cross-plugin sequencing, spec and UAT gates, artifact review, DevOps risk controls, docs governance, session supervision, and hook-enforced delivery gates.
The most important gains are practical: fewer skipped steps, stronger traceability, better artifact quality, safer DevOps work, and clearer release readiness.
SB records skill use, blocks code edits before planning, blocks direct planning-file edits, prevents state tampering, blocks red-CI pushes, and stops completion when required gates are missing.
GSD has gsd:do; SB’s value is composing a broader task-specific chain for feature, bugfix, UI, DevOps, research, release, or fast-path work.
SB sequences GSD with selected helper plugins for review, design, Product Management, DevOps enrichments, and SB-owned gates into one governed process.
silver:spec, silver:ingest, silver:validate, spec-floor checks, UAT gates, and PR traceability connect accepted requirements to delivery evidence.
Product work gets 8 core dimensions, with AI/LLM safety added where applicable. DevOps work gets seven IaC-adapted dimensions before high-risk implementation.
/verify-tests runs configured commands, writes a session freshness marker, invalidates it after source edits, and blocks stale PR/deploy/release attempts.
SB adds release-gate architecture around GSD milestone completion. The full four-stage pre-release gate is currently proven for this Claude/Codex plugin project and should be generalized.
Blast-radius ratings, incident paths, CAB hard stops, environment promotion, deploy checklists, rollback/runbook requirements, and IaC routing reduce production risk.
SB protects GSD-owned planning files, SB state markers, legacy bypass markers, instruction files, and third-party plugin surfaces from unsafe direct edits.
Roadmap freshness, spec-session capture, PR traceability blocks, validation warnings, implementation links, and phase archives reduce artifact drift and data loss.
SB reviews specs, requirements, design, roadmap, context, research, ingestion manifests, UAT, and cross-artifact consistency with audit trails and analytics.
/silver-add, /silver-rem, /silver-scan, and /silver-handoff convert deferred items, lessons, knowledge, and session residue into durable memory.
SB investigates enforcement failures, stalls, abandoned sessions, hook failures, wrong output, and task-level drift beyond GSD’s planning-artifact forensics.
UserPromptSubmit hooks, semantic compression, session logs, timeout sentinels, branch warnings, and anti-stall messages keep process state visible in long sessions.
SB shows live workflow progress on tool use, including composed-flow progress or required-skill progress, so the missing next step is visible before finalization.
silver:fast keeps small edits lightweight while preventing agents from directly arming legacy bypass markers or treating DevOps files as harmless text.
Phase locks, runtime identities, heartbeats, stale-lock handling, and controlled delegation let multiple SB-bearing hosts share a worktree more safely.
Doc schemes, doc checklists, silver:ensure-docs, brownfield reconciliation, and doc freshness gates make durable documentation part of delivery.
Security, quality, GSD verification, review, release, UAT/spec, ingestion review, and acceptance coverage gates are explicit policy boundaries.
Silver Bullet is strongest when the ownership line is clear: GSD remains the execution engine, while SB supplies orchestration and enforcement around it.
| Capability | Owner | Why It Is Not An SB-Over-GSD Benefit |
|---|---|---|
.planning/ lifecycle | GSD | SB reads and gates around it; GSD writes and owns the core lifecycle artifacts. |
| Roadmap, phase, state, and project artifacts | GSD | SB protects and audits these files, but it does not replace their ownership. |
| Phase discussion, planning, execution, and verification | GSD | SB sequences these steps; GSD performs them. |
| Wave-based parallel execution | GSD | SB may invoke the execution path, but GSD supplies the mechanism. |
| Fresh agent execution context | GSD | This is GSD’s core execution advantage, not a new SB capability. |
| Atomic per-task commits | GSD | SB permits intermediate commits through enforcement; GSD creates the atomic task commits. |
| Dimension | Plain GSD | Silver Bullet + GSD |
|---|---|---|
| Primary role | Planning and execution engine | Orchestration and enforcement layer around GSD |
| User entry point | gsd:* commands and gsd:do | /silver classifies intent and composes the SB/GSD/plugin chain |
| Process discipline | Instructional and artifact-driven | Hook-enforced and state-tracked |
| Spec lifecycle | Requirements and plans live in GSD artifacts | SPEC.md, ingestion, validation findings, UAT gates, and PR traceability |
| Artifact review | Review focused on GSD lifecycle work | General artifact-review framework across specs, design, roadmap, research, UAT, and cross-artifact sets |
| Delivery safety | Mostly operator discipline plus GSD workflow | Mechanical gates on edits, commits, PRs, deploys, releases, docs, CI, and tests |
| DevOps workflow | Can execute infrastructure tasks as project work | Blast radius, incident paths, IaC gates, promotion, deployment safeguards |
Different teams feel the value in different places: clearer acceptance evidence, fewer skipped gates, better project memory, and safer infrastructure changes.
Ask at the task level and get traceable delivery evidence.
Get clearer process boundaries and ownership rules.
Get stronger audit trails and cleaner project surfaces.
Get production-safety practices around GSD execution.
Silver Bullet is not "better GSD." It is a governance layer for projects where process drift, release risk, or traceability gaps matter.
Silver Bullet already adds concrete value around GSD. Two areas are being expanded so that value becomes more generic and more visible during live work.
The release-gate architecture already exists around review, tests, CI, docs, and release readiness. The full four-stage pre-release sequence is strongest in this plugin project today and is being generalized for downstream projects.
The next step is more contextual guidance during live work: what is happening now, why the next gate matters, what evidence was produced, and the shortest safe recovery path when a gate blocks.
The strongest claim is not that SB executes better than GSD. It is that SB makes GSD-backed work more governed, more auditable, and less dependent on the agent remembering every gate.
Install Silver Bullet