skills.rest
Grimblaz
GrimblazCOMMUNITY
Explore all skills by this author →
GitHub

tracking-format

Standardize YAML frontmatter fields in .copilot-tracking files for cross-session context.

3|Updated Dec 7, 2025
Search Tags:#documentation#yaml#coordination#handoff#frontmatter#tracking#copilot-tracking
One-click install
npx skills add https://github.com/Grimblaz/agent-orchestra --skill tracking-format
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tracking-format
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/tracking-format
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill tracking-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracking-file frontmatter and coordination format guidance for .copilot-tracking stores consistent metadata across work sessions. DO NOT USE FOR: session-memory plan authoring rules outside the documented references here.

Core Features & Use Cases

  • Defines the required YAML frontmatter fields (status, priority, issue_id, created) and optional fields (tags, updated, assigned_agent, blocked_by, related_issues) for tracking and handoff.
  • Describes standard value ranges for status and priority and explains archiving rules for completed work.
  • Provides guidelines for writing clean, cross-session tracking notes and prompts.

Quick Start

Create or review a tracking file by adding YAML frontmatter with status, priority, issue_id, and created fields at the top.

Frequently Asked Questions about tracking-format

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

FAQPage Schema
How do I standardize tracking file metadata to preserve context across work sessions?▼

To standardize tracking file metadata, add YAML frontmatter with required fields like status, priority, issue_id, and created at the top of your files. This preserves consistent context for cross-session handoffs.

What YAML frontmatter fields are required for copilot-tracking handoffs?▼

Required YAML frontmatter fields for copilot-tracking handoffs include status, priority, issue_id, and created. Optional fields like tags, updated, assigned_agent, blocked_by, and related_issues can also be added.

When do I need to use a standardized tracking format for coordination?▼

You need a standardized tracking format when creating, updating, or reviewing local tracking files and handoffs within Copilot-oriented workflows to ensure consistent metadata and context across sessions.

Does the tracking format specify archiving rules for completed work?▼

Yes, the tracking format describes standard value ranges for status and priority and explains archiving rules specifically for completed work to keep your tracking stores clean.

Can I use this tracking format for session-memory plan authoring outside of handoffs?▼

No, you should not use this tracking format for session-memory plan authoring rules outside the documented references. It is specifically for tracking file frontmatter and coordination format guidance.

Related Skills

Explore More Content & Communication Skills→
ThedouglerThedougler

make-skill-template

Scaffold GitHub Copilot Agent Skills with a SKILL.md file and YAML frontmatter.

Community
Basic
ydnikolaevydnikolaev
8

doc-janitor

Validate YAML frontmatter and migrate documents across lifecycle folders.

Community
Intermediate
swannysecswannysec
3

session-handoff

Generate a structured handoff package with context snapshot for cross-session continuity.

Community
Advanced
thieungthieung
1

session-sync

Export Claude Code sessions into structured Markdown with frontmatter metadata.

Community
Intermediate