create-artifact

Create Artifact

Register your deliverable through the configured content provider with mcp__plugin_dh_backlog__artifact_register, or use the artifact register CLI subcommand in scripting contexts. Pass the content in the registration call and return only its logical ID.

Storage boundary

• artifact_register writes through the selected provider; agents do not choose or access its storage layer.
• artifact_read(item_id, artifact_type) retrieves the current artifact through the same boundary.
• Background agents return the logical ID instead of repeating the document in their completion message.

Invocation

MCP:

mcp__plugin_dh_backlog__artifact_register(
    item_id=<int | str>,          # Backlog item identifier — REQUIRED
    artifact_type=<str>,          # Artifact type string — REQUIRED (see table below)
    artifact_id=<str>,            # Logical identifier — REQUIRED
    status="current",             # Lifecycle status: draft | current | superseded | archived
    agent=<str>,                  # Name of the producing agent (default: "")
    content=<str>,                # Non-empty full artifact content — REQUIRED
)

CLI equivalent (scripting/dispatch contexts):

uv run "${CLAUDE_PLUGIN_ROOT}/sam_schema/cli.py" artifact register \
  --item-id <identifier> \
  --artifact-type <str> \
  --artifact-id <str> \
  --status "current" \
  --agent <str> \
  --content <str>

--status and --agent are optional (same defaults as the MCP form). The examples below use the MCP form; substitute the same values into the CLI flags above for a scripting context.

Return value: dict with keys registered (bool), artifact_count (int), action ("added" or "updated"), content_stored (bool), messages, warnings. Check action in your STATUS: DONE report — do NOT paste the full content.

Parameters

artifact_type

One of the recognized type strings:

artifact_type	Producing agent	When to use
feature-context	feature-researcher	Discovery document: WHO/WHAT/WHEN/WHY analysis
codebase-analysis	codebase-analyzer, code-review-architecture	Codebase pattern/architecture/testing documents and dependency graphs; several per item
code-review	code-reviewer	Code review verdict; one per reviewed task, read by the quality gate via artifact_id
architect	{resolved_agent} (language-plugin design-spec agent, resolved via profile_list)	Architecture spec with interfaces and contracts
T0-baseline	t0-baseline-capture	Pre-implementation baseline of acceptance criteria
TN-verification	tn-verification-gate	Post-implementation verification results
research	any research agent	Investigation findings, coverage analysis, rationale
task-plan	sam_plan (internal, auto-registered)	Never call artifact_register directly for this type — see task-plan below
dispatch-plan	dispatch_create_plan (internal, auto-registered)	Milestone dispatch plan; created automatically by the dispatch_create_plan MCP tool, not by direct registration
audit-report	doc-drift-auditor	Documentation drift audit findings for a completed work item