메뉴
Maintain durable feature-level memory across AI coding sessions with lightweight Markdown tracks for status, source-of-truth docs, decisions, risks, and changes.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/ranbot-ai/awesome-skills --skill feature-tracking명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Generate project-specific AGENTS.md and companion rules by analyzing a codebase. Supports full, minimal, update, and dry-run modes with package-manager detection, monorepos, backups, managed blocks, c
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release
Provision backend infra through Cohesivity (cohesivity.ai): Postgres, hosting, auth, storage, and AI model APIs over one HTTP API. Use when a .cohesivity file exists or a project needs a backend.
SOC 직업 분류 기준
| name | feature-tracking |
| description | Maintain durable feature-level memory across AI coding sessions with lightweight Markdown tracks for status, source-of-truth docs, decisions, risks, and changes. |
| category | Document Processing |
| source | antigravity |
| tags | ["markdown","api","claude","ai","agent","automation","workflow","design","document","security"] |
| url | https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/feature-tracking |
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.
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.
Before changing a feature:
docs/features/README.md if it exists.docs/features/<feature-id>/README.md if it exists.Never assume an old plan is authoritative merely because it is detailed. Prefer current code, tests, accepted specifications, and recent verified decisions.
Use lowercase hyphen-case for feature ids:
docs/features/
├── README.md
└── <feature-id>/
├── README.md
├── prd/
├── api/
├── plans/
└── archive/
For an existing repository, create only the directories needed now. Link useful documents where they already live before considering a migration.
The global index should remain a compact navigation and status surface:
# Feature Tracks
| Feature | Status | Track | Source of Truth | Updated | Notes |
|---|---|---|---|---|---|
| Checkout | active | `checkout/README.md` | `checkout/prd/checkout.md` | 2026-07-13 | Payment retry work in progress |
Use project-local status names when the repository already defines them. Otherwise prefer a small vocabulary such as planned, active, stable, paused, or deprecated.
Each docs/features/<feature-id>/README.md should summarize current truth and link to detailed evidence:
# Checkout Feature Track
## Current Status
Checkout supports one-time card payments. Automatic payment retry is in progress.
## Source of Truth
- Checkout PRD: `prd/checkout.md`
- Payments API: `api/payments.md`
- Current implementation plan: `plans/payment-retry.md`
## Current Behavior
- Customers can complete one-time card payments.
- Failed payments currently require a manual retry.
## Decisions
- Preserve idempotency keys across automatic retries.
- Keep retry policy in the payments service.
## Known Risks
- The provider sandbox does not reproduce every production decline code.
## Changelog
- 2026-07-13: Added the retry plan and recorded idempotency requirements.
Update the track when any of these change:
Keep detailed requirements and designs in their own documents. The feature track should explain what is true now and where to find the proof.
Before claiming the feature work is complete:
User: Continue the checkout retry feature and make sure the next agent understands what changed.
Agent workflow:
1. Read docs/features/README.md and docs/features/checkout/README.md.
2. Open the linked PRD, API notes, and current implementation plan.
3. Verify the existing behavior in code and tests.
4. Implement and test the requested retry behavior.
5. Update Current Behav