artifact-conventions

Name: artifact-conventions
Availability: InStock
Author: patrickrmoore

Enforce preservation, format, and section conventions for spec artifacts.

Updated Mar 22, 2026

Search Tags:#versioning #governance #spec #traceability #artifact #specs

Ready to run

npx skills add https://github.com/patrickrmoore/sdd-test --skill artifact-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: artifact-conventions
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/artifact-conventions
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill artifact-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/<feature-folder>/ to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.

Core Features & Use Cases

Enforces consistent frontmatter structure and required sections in spec-related artifacts.
Guards cross-artifact references, IDs, and gating state to maintain traceability.
Applies to files under specs/<feature-folder>/ to ensure governance and consistency across the feature workspace.

Quick Start

Edit artifact files under specs/<feature-folder>/ to automatically apply the conventions.

Frequently Asked Questions about artifact-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain cross-artifact traceability when editing spec files?▼

To maintain cross-artifact traceability when editing spec files, enforce preservation rules for cross-referenced IDs, priorities, and gating state to prevent accidental corruption of linked artifacts during edits.

What are frontmatter validation rules for spec and plan artifacts?▼

Frontmatter validation rules for spec and plan artifacts require consistent frontmatter structure and specific section presence to ensure artifact integrity and governance across the feature workspace.

How do I prevent accidental changes to gating state in feature specs?▼

Preventing accidental changes to gating state in feature specs requires enforcing non-destructive edits and preservation conventions, protecting critical cross-referenced state values from being overwritten during routine artifact updates.

When do I need specification governance conventions for feature artifacts?▼

You need specification governance conventions for feature artifacts when editing files under specs/<feature-folder>/ to prevent changes to IDs, priorities, and gating state, ensuring consistency and traceability across the feature workspace.

Does artifact convention enforcement work with existing spec.md and plan.md files?▼

Artifact convention enforcement works with existing spec.md and plan.md files by applying preservation, format, and section rules automatically when editing, guarding cross-artifact references without requiring file migration.