skills.rest
dpaola2
dpaola2COMMUNITY
Explore all skills by this author →
Website𝕏@dpaola2GitHub

backfill-timing

Retrofit YAML frontmatter with pipeline timing metadata from Git commit timestamps.

3|Updated Feb 18, 2026
Search Tags:#git#yaml#metadata#pipeline#timing#backfill
One-click install
npx skills add https://github.com/dpaola2/pipeline-skills --skill backfill-timing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backfill-timing
Source: https://github.com/dpaola2/pipeline-skills/tree/main/.claude/skills/backfill-timing
Command: npx skills add https://github.com/dpaola2/pipeline-skills --skill backfill-timing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of missing pipeline timing metadata in older project documents by retrofitting YAML frontmatter with historical data.

Core Features & Use Cases

  • Retroactive Metadata Addition: Adds pipeline_stage, pipeline_completed_at, and pipeline_approved_at to existing documents.
  • Data Source Prioritization: Intelligently uses Git commit timestamps, document header dates, and approval checklist dates to infer timing.
  • Use Case: For a project completed before timing was tracked, this Skill can automatically add the necessary metadata to prd.md, architecture-proposal.md, and other key documents, enabling accurate pipeline metrics.

Quick Start

Use the backfill-timing skill to retrofit pipeline timing metadata onto all artifacts for work item SN-3.

Frequently Asked Questions about backfill-timing

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

FAQPage Schema
How do I backfill pipeline timing metadata into existing project documents?▼

The skill retrofits YAML frontmatter onto existing documents by adding pipeline_stage, pipeline_completed_at, and pipeline_approved_at fields to backfill pipeline timing metadata using inferred historical data.

How does Git timestamp prioritization work when adding historical metadata to markdown files?▼

Git commit timestamps are checked first, then document header dates, and finally approval checklist dates to infer timing for YAML frontmatter fields when adding historical metadata.

Can I add pipeline_completed_at fields to multiple document types like PRDs and architecture proposals?▼

You can add pipeline_completed_at fields to multiple document types including PRDs, discovery reports, architecture proposals, gameplans, test matrices, progress reports, and QA plans.

Do I need Git installed to retroactively add YAML frontmatter to old project artifacts?▼

Git is a required dependency because the skill prioritizes Git commit timestamps as the primary data source to infer and backfill historical pipeline timing metadata.

What is the best way to track pipeline metrics for projects completed before timing was recorded?▼

To track pipeline metrics for older projects, automatically retrofit the necessary timing metadata onto key documents like prd.md to enable accurate historical pipeline metric calculation.

Related Skills

Explore More Software Engineering Skills→
OzeroHAXOzeroHAX
32

shared-docs-paths

Define hierarchical paths and purposes for project documentation files.

Community
Basic
dpaola2dpaola2
3

metrics

Compute pipeline timing metrics from YAML frontmatter and Git/PR data.

Community
Advanced
mixelpixxmixelpixx
252

fact-check

Verify factual claims against multiple authoritative sources with structured evidence.

Community
Intermediate
guanyangguanyang
947

baoyu-format-markdown

Format Markdown files with YAML frontmatter and normalized typography.

Community
Intermediate