Agent skill · operations · sickn33
feature-tracking
Maintain durable feature-level memory across AI coding sessions with lightweight Markdown tracks for status, source-of-truth docs, decisions, risks, and changes.
Why this skill is useful
Provides a structured approach to feature tracking that enhances AI agents' ability to maintain context and continuity across coding sessions.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Feature Tracking Overview Feature Tracking maintains lightweight, repository-native memory for long-lived feature work. It gives AI coding agents a stable place to find the current status, authoritative documents, verified behavior, durable decisions, risks, and recent changes without treating chat history or stale plans as truth. The workflow uses a global index plus one Markdown track per feature under docs/features/. It complements issue trackers, specifications, and source code by linking the evidence that still matters rather than duplicating it. When to Use This Skill Use when starting or resuming work on a feature after a session, agent, or tool change. Use when feature knowledge is scattered across PRDs, API notes, plans, issues, and old commits. Use when a long-lived feature needs durable decisions, risks, rollout constraints, or migration notes. Use when reviewing or finishing feature work and recording the verified outcome for future agents. Use when adopting lightweight project memory in an existing repository without reorganizing all documentation. Do not use this skill merely to log every code edit or replace an existing issue tracker. Use it when future contributors need a concise, current view of an entire feature. How It Works Step 1: Discover Existing Feature Memory Before changing a feature: 1. Read docs/features/README.md if it exists. 2. Identify the feature id from the request, code module, route, domain, or existing documentation. 3. Read docs/features/<feature-id>/README.md if it exists. 4. Follow its current source-of-truth links before proposing or implementing changes. Never assume an old plan is authoritative merely because it is detailed. Prefer current code, tests, accepted specifications, and recent verified decisions. Step 2: Create the Minimal Structure When Missing Use lowercase hyphen-case for feature ids: For an existing repository, create only the directories needed now. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/feature-tracking--5a2800