Overview
/silver:ingest imports external product and design context into Silver Bullet's planning artifacts. It never calls APIs directly; all external data access is delegated to configured MCP connectors.
The workflow is resumable through .planning/INGESTION_MANIFEST.md. Successful artifacts are skipped on later runs, while failed artifacts remain visible and actionable.
Supported Sources
| Source | How it is handled |
|---|---|
| JIRA | Fetch issue summary, description, acceptance criteria, links, and attachments metadata via Atlassian MCP. |
| Confluence | Resolve Confluence links found in ticket descriptions and include fetched page content in spec context. |
| Figma | Requires the user to select target frames in Figma before MCP extraction. Produces design context and tokens for DESIGN.md. |
| Google Docs | Reads document text through Google Drive MCP when available; fallback behavior is explicit and source-aware. |
| Cross-repo spec | --source-url mode fetches an upstream repo spec and pins version context for multi-repo coordination. |
Outputs
.planning/SPEC.md— created or augmented from source context..planning/DESIGN.md— created when Figma or design source context is available..planning/INGESTION_MANIFEST.md— source-by-source audit trail of success, failure, and extraction status.
Workflow Steps
- Mode detection: choose artifact-ingest or cross-repo-fetch mode.
- Connector check: detect Atlassian, Figma, and Google Drive MCP availability.
- JIRA and link resolution: fetch ticket context and queue linked design or doc artifacts.
- Figma extraction: wait for explicit user confirmation after target frames are selected.
- Google Docs extraction: read document content when connector access is available.
- Assemble drafts: write or augment SPEC.md and DESIGN.md from extracted context.
- Manifest review: write INGESTION_MANIFEST.md and run artifact review to two consecutive clean passes.
Failure Handling
Connector failures do not silently block the whole ingestion run unless they prevent required output generation. Instead, each failed artifact is recorded with status and reason, and the spec receives an explicit [ARTIFACT MISSING: ...] block in the section where that content was expected.
That behavior keeps downstream GSD planning honest: implementers can see which requirements came from source material and which areas still need human follow-up.
Spec Handoff
After ingestion, run /silver:spec if the imported material needs additional elicitation, or /silver:validate if plans already exist and need coverage analysis.