pipeline-artifacts

Create and validate YAML/MD artifact schemas for pipeline stages.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill pipeline-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-artifacts
Source: https://github.com/hoshiyar-singh8/SprintPlanner/tree/main/skills/pipeline-artifacts
Command: npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill pipeline-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YAML/MD schemas and background guidance for managing pipeline artifacts across stages.

Core Features & Use Cases

  • Artifact Directory guidance: default location and usage rules.
  • Artifact Inventory: templates for tracking files like feature_input.yaml, clarifications.md, context_pack.yaml, high_level_plan.md, etc.
  • Reference schemas: provides templates for the various pipeline artifact schemas and their consumption.
  • Use Case: teams standardize artifacts to enable automation, reproducibility, and smooth handoffs between stages.

Quick Start

Create or validate the feature's artifact schemas using the defined templates and update the artifact inventory accordingly.

Frequently Asked Questions about pipeline-artifacts

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

FAQPage Schema
How do I standardize pipeline artifacts for feature inputs and plans?

To standardize pipeline artifacts, use YAML and Markdown templates to define and validate schemas for feature inputs, clarifications, and high-level plans. This ensures consistency across pipeline stages and maintains traceability to the feature name.

What is an artifact inventory and how does it organize pipeline stages?

An artifact inventory is a tracking system using templates to manage files like feature_input.yaml, clarifications.md, and context_pack.yaml. It organizes pipeline stages by maintaining consistency and ensuring smooth handoffs between teams.

How do I create and validate artifact schemas using YAML templates?

Create and validate artifact schemas by applying predefined YAML and Markdown templates to your feature's inputs and plans. Update the artifact inventory accordingly to maintain traceability and ensure all files conform to the established structure.

Do I need any specific dependencies to use YAML and MD schemas for pipeline automation?

No specific dependencies are required to use these YAML and MD schemas for pipeline automation. The templates provide background guidance and reference schemas that can be applied directly to manage artifacts across pipeline stages.

What is the best way to track feature inputs and clarifications across pipeline stages?

The best way to track feature inputs and clarifications is by maintaining an artifact inventory with standardized YAML and MD files. This enables reproducibility, automation, and smooth handoffs by ensuring all artifacts are documented and traceable.

Why does my pipeline artifact schema lack consistency across different stages?

Pipeline artifact schemas lack consistency when teams do not use standardized templates for inputs, clarifications, and plans. Applying defined YAML and MD schemas and updating an artifact inventory ensures traceability and uniform organization across all stages.