git404hub

what is feature-track fr?

junsw/feature-track — explained in plain English

Analysis updated 2026-05-18

121PythonAudience · developerComplexity · 2/5LicenseSetup · easy

tl;dr

Feature Track is a Markdown based memory system stored inside your repo that keeps AI coding agents like Claude Code and Codex up to date on each feature's status, decisions, and current source of truth.

vibe map

mindmap
  root((Feature Track))
    What it does
      Tracks feature memory
      Lives in docs folder
      Global feature index
    Tech stack
      Python CLI
      Markdown files
      Claude Code plugin
    Use cases
      Onboard new agent sessions
      Validate doc drift
      Record feature decisions
    Audience
      Solo developers
      Small teams
    Setup
      One command install
      Works with existing docs

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Give an AI coding agent a durable memory of what each feature in your repo currently is and why.

VIBE 2

Stop agents from rediscovering the same project context every time you start a new session.

VIBE 3

Validate that your feature documentation index has not drifted or gone stale.

VIBE 4

Adopt a lightweight memory layer on a brownfield project without rewriting existing docs.

what's the stack?

PythonMarkdownClaude CodeCodex

how it stacks up fr

junsw/feature-track2417467487-hub/worldcuproichefkannofriend-source/lcb-baker-agent
Stars121121121
LanguagePythonPythonPython
Setup difficultyeasymoderateeasy
Complexity2/54/52/5
Audiencedeveloperpm foundergeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min
MIT license: use, modify, and distribute freely, including for commercial projects, as long as you keep the copyright notice.

in plain english

Feature Track is a lightweight, repo-native way to keep AI coding agents like Codex and Claude Code aligned on what each long-lived feature in a project actually is, right now. Instead of a chat history search or a database, it is a set of Markdown files that live inside your own repository under docs/features, one per feature plus a global index. The problem it addresses is that AI coding agents are good at making changes but bad at holding onto context. Feature knowledge tends to be scattered across product docs, API notes, plans, old chats, and commits, so agents often rediscover the same things repeatedly, and stale plans can look authoritative even after the real system has moved on. Switching between tools or sessions usually resets whatever memory an agent had built up. Feature Track gives each important feature a small living file that records its current status, which docs are still the real source of truth, key decisions, risks, and recent changes, without replacing the existing documentation it points to. It is aimed at teams and solo developers who want shared project memory without a heavy process, especially brownfield projects with useful but scattered documentation, and anyone using Codex, Claude Code, or several agent tools together. The design favors linking to existing docs first and migrating content later, so it can be adopted gradually rather than requiring a full rewrite of a project's documentation. Installation is a single command, npx skills add JunsW/feature-track, with alternate paths for installing it as a Codex plugin, a Claude Code plugin, or through local Python adapters. A companion CLI can initialize the feature index, add new feature tracks, and validate that the index has not drifted, required sections are present, and internal links are not broken. Validation is intentionally lenient by default so it can be tightened later in continuous integration. Feature Track describes itself as lighter than full spec-driven development frameworks, since it focuses on remembering what a feature is rather than governing every step of building it. The project is licensed under the MIT license and is currently at version 0.1.0, its first public release.

prompts (copy fr)

prompt 1
Install Feature Track in my repo with npx skills add JunsW/feature-track and set up the first feature index.
prompt 2
Create a Feature Track entry for this feature describing its current status and source of truth docs.
prompt 3
Run Feature Track's validate command and fix any index drift or broken links it finds.
prompt 4
Explain how Feature Track differs from a full spec-driven development framework.

Frequently asked questions

what is feature-track fr?

Feature Track is a Markdown based memory system stored inside your repo that keeps AI coding agents like Claude Code and Codex up to date on each feature's status, decisions, and current source of truth.

What language is feature-track written in?

Mainly Python. The stack also includes Python, Markdown, Claude Code.

What license does feature-track use?

MIT license: use, modify, and distribute freely, including for commercial projects, as long as you keep the copyright notice.

How hard is feature-track to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is feature-track for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.