aidlc-tracking

Scaffold per-repo tracking files for AI development lifecycles.

13|3|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/indranildchandra/claude-local-starter --skill aidlc-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-tracking
Source: https://github.com/indranildchandra/claude-local-starter/tree/main/skills/aidlc-tracking
Command: npx skills add https://github.com/indranildchandra/claude-local-starter --skill aidlc-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI Development Lifecycle tracking standardizes how project state and decisions are recorded, ensuring consistency across repositories and teams.

Core Features & Use Cases

  • Per-repo canonical formats: Provides templates and rules to store tracking data per repository.
  • Guided workflows: Prepares files for plan, tracker, changelog, and design reviews, facilitating audits and governance.
  • On-demand scaffolding: Creates or initializes required tracking files and formats when a new repo is started or major changes happen.
  • Integration with DX tools: Works with gitnexus, context tooling, and format references to maintain a living knowledge graph.
  • Use Case: When kicking off a project, you run the skill to scaffold all tracking files and set up standard reviews and progress logs.

Quick Start

Initialize AIDLC tracking for your repository by loading the formats and creating the per-repo tracking files using the skilled workflow.

Frequently Asked Questions about aidlc-tracking

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

FAQPage Schema
How do I standardize per-repo tracking files for AI-driven development?

Per-repo tracking for AI development is standardized by applying templates and write rules to scaffold plan, tracker, changelog, and design review files. It ensures consistent project state records by loading formats.md before writing.

When do I need to scaffold tracking files in my repository?

Scaffolding tracking files is needed when initializing a new repository, during design reviews, or after major refactors. This ensures the AI development lifecycle maintains consistent tracking data and format governance.

What is the best way to maintain a knowledge graph for AI development lifecycles?

Maintaining a knowledge graph for AI development is best achieved by integrating per-repo tracking files with gitnexus and context tooling. This standardizes formats and automates governance across repositories.

Does this tracking workflow require specific formats before writing to files?

Yes, this tracking workflow requires formats.md to be loaded before writing to per-repo tracking files. This ensures all templates and write rules are applied correctly for governance.

Can I use gitnexus to integrate with per-repo tracking formats?

Yes, you can integrate gitnexus with per-repo tracking formats. This skill works with gitnexus and context tooling to maintain a living knowledge graph and apply governance across repositories.