Reading Artifacts
The Rule
Use the MCP tools. Don't construct paths. Don't search.
- •
list_artifacts- See what artifacts exist - •
get_artifact- Get content and metadata by filename
Reading an Artifact
code
# List what's available
list_artifacts
→ { "artifacts": [{ "filename": "refinement.md", ... }] }
# Get specific artifact
get_artifact({ "filename": "refinement.md" })
→ { "filename": "refinement.md", "content": "...", ... }
After you have successfully gotten an artifact.
use the skill: potato:notify-user to announce:
"[Your Agent Name]: I found the following artifact and will read it as a part of my context."
Common Artifacts
| Artifact | Phase | Description |
|---|---|---|
refinement-draft.md | Refinement | Initial requirements (may have gaps) |
refinement.md | Refinement | Approved requirements |
architecture-draft.md | Architecture | Initial technical design |
architecture.md | Architecture | Approved technical design |
specification.md | Specification | Final spec with tasks |
Red Flags - STOP Immediately
| Thought | Reality |
|---|---|
| "Let me construct the path" | Use get_artifact instead |
| "Let me search for refinement.md" | Use list_artifacts to see what exists |
| "I'll use the Read tool" | Use get_artifact - it handles paths |
| "Maybe it's in ~/.potato-cannon/" | MCP tools abstract storage location |
The Contract
- •Always use MCP tools -
list_artifactsandget_artifact - •Never construct paths - The tools handle path conversion
- •Check before reading - Use
list_artifactsif unsure what exists