Set a tracking document as the source of truth for the current feature or task.
NewMaintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Project Management pack
Last verified 8/20/2026
What it changes
5 of 22 test cases passed with the skill.
Pass-rate lift
—
Tokens
-9%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/20/2026v15 of 22 cases passed with skill · 7 comparable
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 7 comparable cases; this report requires 8.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Document the setup steps for our Redis cluster in `docs/redis-setup.md` based on our discussion about primary node configuration, failover timeouts, and replication factor.
What was checked, without and with the skill
Checked
Without skill
With skill
Formats entries in `docs/redis-setup.md` using bullet points rather than paragraphs.
Missed
Passed
case-08 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md32 linessingle file
Working On
You are managing a tracking document that serves as the source of truth for the current task or feature.
The tracking document is: $path
Behavior
Once activated, treat the tracking document as a living record. Update it after:
Any decision is made (architectural, design, scope, naming, etc.)
A new problem, bug, or edge case is discovered
A new sub-feature or requirement emerges
An issue is raised or resolved
Any significant implementation work is completed
A key part of a conversation with the user that would be useful to recall later
Any time you commit files — a commit is a strong signal that the tracking document should also be reviewed and updated
Any plan you form — write it to the document rather than presenting it only in chat; the document is the persistent record
If in doubt, update the document. It is better to over-document than to lose context.
Git Handling
Do NOT commit the tracking document unless it already appears in the repository's git history. If the file is not tracked by git, leave it out of any commits.
Guidelines
Keep updates concise — bullet points and short paragraphs are preferred over prose
Use timestamps or date headers when the document spans multiple sessions
Record the why behind decisions, not just the what
When a section becomes stale or irrelevant, move it to an "Archive" or "Resolved" section rather than deleting it
If the document doesn't exist yet, create it with a sensible structure based on the task at hand