artifact-frontmatter

Validate YAML frontmatter schema for pipeline artifacts in docs/plans.

8|1|Updated Mar 28, 2026

Search Tags:#automation #workflow #schema #governance #pipeline #frontmatter

Ready to run

npx skills add https://github.com/bostonaholic/team --skill artifact-frontmatter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: artifact-frontmatter
Source: https://github.com/bostonaholic/team/tree/main/skills/artifact-frontmatter
Command: npx skills add https://github.com/bostonaholic/team --skill artifact-frontmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents configuration drift and state inconsistency in complex multi-agent workflows by enforcing a strict YAML frontmatter schema across all pipeline artifacts.

Core Features & Use Cases

Schema Enforcement: Validates the mandatory frontmatter fields for task, research, design, and plan documents.
Design Review Tracking: Manages the lifecycle of design-review records, including verdict tracking and revision capping.
Multi-Repo Coordination: Provides the logic for the repos.md artifact, enabling the pipeline to switch between single-repo and multi-repo worktree modes.

Quick Start

Ask the assistant to validate the frontmatter of the current artifact in the docs/plans directory to ensure it meets the required schema contract.

Frequently Asked Questions about artifact-frontmatter

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

FAQPage Schema

How do I enforce YAML frontmatter schema validation for autonomous agent pipeline artifacts?▼

Enforce YAML frontmatter schema validation by applying strict rules to mandatory fields within task, research, design, and plan documents. This process prevents configuration drift and ensures state consistency across complex multi-agent workflows operating within the docs/plans directory.

Why does configuration drift occur in multi-agent workflows and how can frontmatter prevent it?▼

Configuration drift occurs in multi-agent workflows when pipeline artifacts lack strict structural rules. Enforcing a standardized YAML frontmatter schema prevents this drift by validating mandatory fields and maintaining topic consistency across all task, research, and design documents.

How do I track design-review state and verdicts across multi-agent pipeline artifacts?▼

Track design-review state by implementing strict frontmatter schema validation for design records. This manages the lifecycle of design-review artifacts, including tracking verdicts and capping revisions to ensure pipeline reliability across autonomous agent workflows.

Can I use frontmatter schema rules to switch between single-repo and multi-repo worktree modes?▼

Yes, frontmatter schema rules support switching between single-repo and multi-repo worktree modes. The validation logic processes the repos.md artifact to provide the necessary coordination logic for multi-repo pipeline execution.

What mandatory frontmatter fields are required for task and research artifacts in a docs/plans directory structure?▼

Mandatory frontmatter fields for task and research artifacts include schema elements for topic consistency, design-review state tracking, and phase-gating logic. Strict validation ensures these documents meet the required schema contract for autonomous agent pipelines.

When do I need strict frontmatter validation for pipeline artifacts?▼

You need strict frontmatter validation for pipeline artifacts when managing complex multi-agent workflows. It is required to prevent configuration drift, maintain state consistency, and ensure phase-gating reliability across task, research, design, and repository-mapping artifacts.