artifact-templateslisted

# Artifact Templates Centralized output templates for all rp1 artifact types. Agents read templates to produce correctly formatted, correctly routed artifacts. ## Usage 1. Read this SKILL.md to find the template for your artifact type in the index below. 2. Read the template file at the listed path (relative to this skill directory). 3. Fill placeholders (`{FEATURE_ID}`, `{Date}`, `[bracketed text]`) with actual values. 4. Write the artifact to the location specified by `scope` + `path_pattern`. 5. If the template includes `emit_hint`, the producer MUST register the artifact after writing it. Templates contain YAML frontmatter with routing metadata and a markdown body with the artifact format. Section-level templates (`type: section`) are appended to existing files, not written as standalone documents. Active `/build` artifacts are producer-owned: the agent that writes the artifact registers that exact path with explicit `storageRoot`. Do not recover active build artifacts by directory scan. Do not generate or register legacy `tracker.md` or `milestone-*.md` artifacts for new work. ## Template Index | Producer | Artifact | Type | Scope | Path Pattern | Template Path | |----------|----------|------|-------|--------------|---------------| | feature-requirement-gatherer | requirements.md | document | workRoot | features/{FEATURE_ID}/requirements.md | templates/feature-requirement-gatherer/requirements.md | | feature-architect | design.md | document | workRoot | features/{