sdd-tracker

Creates and maintains the sdd-tracker.yml file tracking SDD artifact status and history.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-tracker-alessioscarfone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-tracker
Source: https://github.com/AlessioScarfone/aine-copilot-plugins/tree/main/src/sdd-team/skills/sdd-tracker
Command: npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-tracker-alessioscarfone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? In a Specification-Driven Development workflow, multiple artifacts (PRDs, architecture docs, UX specs, change proposals) are produced by different skills, and teams lose track of what exists, when it changed, and what stage each change is in. This Skill maintains a single YAML tracker file as the source of truth for all SDD artifact status and history. ## Core Features & Use Cases - Tracker Initialization: Creates sdd-tracker.yml from a template with project name and creation dates when the file is missing. - Shared Artifact Tracking: Updates created/lastUpdate timestamps and changelog entries for shared artifacts like PRD, architecture, and UX documents. - Change Lifecycle Management: Records change entries and transitions their status through ready-for-dev, in-progress, done, verified, and archived states. - Use Case: When sdd-implement finishes all tasks for a change, this Skill automatically updates the change status to done, stamps lastUpdate, and appends an "Implementation complete" changelog note. ## Quick Start This internal skill is invoked automatically by other SDD workflow skills such as sdd-prd, sdd-propose, and sdd-implement whenever they produce or modify an SDD artifact.

Frequently Asked Questions about sdd-tracker

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

FAQPage Schema
How do I track SDD artifact status across a project?▼

Use a single sdd-tracker.yml file in the artifact main folder as the source of truth. Each SDD workflow skill updates it automatically with created dates, lastUpdate timestamps, status values, and changelog entries whenever artifacts are produced or modified.

What status values does an SDD change go through?▼

Changes follow the sequence ready-for-dev, in-progress, done, verified, and archived. The verified status is set only when verification reports no CRITICAL issues, and archiving requires the change to already be verified.

Can I invoke the sdd-tracker skill directly?▼

No, it is an internal skill marked user-invocable: false. It is auto-invoked by other SDD skills such as sdd-prd, sdd-arch, sdd-ux, sdd-propose, sdd-implement, sdd-verify, and sdd-archive after they produce or modify artifacts.

What happens if the sdd-tracker.yml file does not exist?▼

The skill reads the base template from assets/sdd-tracker.yml, sets the project name from project context such as README or package.json, stamps created and lastUpdate with today's date, and writes the initialized file to the artifact main folder.

Why is a change not being archived in the SDD workflow?▼

Archiving requires the change status to be verified. If verification reported CRITICAL issues or the status is still done or in-progress, sdd-archive will not proceed until verification passes cleanly.