Agent skill · Documentation

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.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill feature-tracking --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Declared author: JunsW
Path: skills/feature-tracking/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. How It Works
  4. Step 1: Discover Existing Feature Memory
  5. Step 2: Create the Minimal Structure When Missing
  6. Step 3: Maintain the Feature Track
  7. Step 4: Reconcile the Track Before Completion
  8. Examples
  9. Example 1: Resume a Feature Across Sessions
  10. Example 2: Adopt Feature Tracking in a Brownfield Repository
  11. Best Practices
  12. Limitations
  13. Security & Safety Notes
  14. Common Pitfalls
More from agentic-awesome-skills
All skills →
About this skill
What does the feature-tracking skill do?

Maintain durable feature-level memory across AI coding sessions with lightweight Markdown tracks for status, source-of-truth docs, decisions, risks, and changes.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill feature-tracking --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going