Overview
/silver:content is the Silver Bullet orchestrator for documentation, copy, and content deliverables — help pages, API docs, README updates, marketing copy, changelogs, and technical writing. It maps to catalog entity WF-SILVER-CONTENT (specialized type) in the v0.48.3 APO catalog.
Content work needs specification discipline without full feature lifecycle overhead. The workflow clarifies audience and tone, specifies structure and acceptance criteria, executes the writing, verifies accuracy and completeness, then documents the deliverable lineage.
Standard composition:
For product feature specs (not content deliverables), use /silver:spec. For research-backed content decisions, start with /silver:deep-research.
AF-VERIFY checks content against source code, APIs, and runtime behavior — documentation that drifts from implementation fails the verify gate.
When to Use
Entry trigger signals for /silver:content, content, and docs:
- Help center pages, API reference, or developer documentation
- README, changelog, or release notes authoring
- Marketing copy, landing pages, or product messaging
- Internal runbooks, onboarding guides, or architecture docs
- Content refresh when implementation has outpaced existing docs
Catalog Composition
| Atomic flow | Command | Outcome |
|---|---|---|
AF-CLARIFY | /silver:clarify | Audience, tone, scope boundaries, and success criteria |
AF-SPECIFY | /silver:spec | Content outline, section structure, acceptance criteria per section |
AF-EXECUTE | /silver:execute | Draft content — prose, code examples, diagrams, metadata |
AF-VERIFY | /silver:verify | Accuracy check against source, link validation, example execution |
AF-DOCUMENT | /silver:ensure-docs | Deliverable packaging, lineage, and publication readiness |
Workflow Steps
AF-CLARIFY — Define audience and scope
Establishes who reads the content (developer, CTO, end user), tone (technical, marketing), scope boundaries, and what "done" looks like.
AF-SPECIFY — Structure the deliverable
Produces a content spec: section outline, required code examples, cross-references, and per-section acceptance criteria. For large doc sets, defines information architecture.
AF-EXECUTE — Write the content
Authors prose, code samples, tables, and diagrams. Follows project style guides and existing doc patterns. May use Composer subagents for public-facing site copy per project policy.
AF-VERIFY — Validate accuracy
Checks code examples compile and run, API references match implementation, links resolve, and terminology is consistent. Drift from source is a verify failure.
AF-DOCUMENT — Package deliverables
Records content lineage, publication paths, and any deferred sections. Ensures docs freshness tests and search index updates are accounted for.
Example Invocation
Silver Bullet routes to WF-SILVER-CONTENT. Clarify defines CTO/dev audience and APO catalog alignment. Specify outlines seven pages with composition chains and acceptance criteria. Execute authors HTML from existing templates. Verify checks catalog slug accuracy and link integrity. Document records the deliverable set for publication.