From context-docs
This skill should be used when maintaining feature context documents in docs/context/. It applies when a project contains a docs/context/ directory, when a feature plan is created or approved, when implementation work is completed, or when the user says "update context doc", "create context doc", "capture context", "feature context", "continue where I left off", "what was built", "document what we built", "save context", "track this feature", or "resume work on".
How this skill is triggered — by the user, by Claude, or both
Slash command
/context-docs:context-trackerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automatically maintain feature context documents at `docs/context/<feature-name>.md` that capture development knowledge — what was built, where changes live, how it works, and why — so future sessions can pick up where work left off.
Automatically maintain feature context documents at docs/context/<feature-name>.md that capture development knowledge — what was built, where changes live, how it works, and why — so future sessions can pick up where work left off.
When docs/context/ exists:
docs/context/INDEX.md to understand existing context documentsWhen docs/context/ does not exist but documentation work begins:
docs/context/ directorydocs/context/INDEX.md using the template from ${CLAUDE_PLUGIN_ROOT}/skills/context-tracker/references/context-template.mdWhen a feature plan is created or approved:
docs/context/ for an existing context doc matching the feature
docs/context/INDEX.mdcontext-summarizer agent (see "Using the Context Summarizer Agent" below)When feature code has been written or a significant implementation milestone is reached:
docs/context/INDEX.mdcontext-summarizer agent (see "Using the Context Summarizer Agent" below)When starting work that may relate to a previous feature:
docs/context/INDEX.md for features related to the current taskContext docs exist within a broader documentation structure:
docs/
context/ ← this plugin manages
prds/ ← prd-manager plugin
plans/ ← AI implementation plans
ROADMAP.md ← high-level project direction
Features.md ← feature summaries
When creating or updating context docs:
docs/prds/ for related PRDs and link them in Related Docsdocs/plans/ for related plans and link themdocs/ROADMAP.md sections if the feature appears theredocs/Features.md entriesEach context doc follows the template at ${CLAUDE_PLUGIN_ROOT}/skills/context-tracker/references/context-template.md.
Key sections:
Append mode (default): Add new entries to existing sections without removing or modifying previous content. Use for iterative development where the feature grows over time.
Rewrite mode: Replace the entire document. Use only when the feature has been fundamentally redesigned. Preserve the original created date and note the rewrite in Architecture Decisions.
To determine the mode: if the current work is a continuation or extension, use append. If the conversation explicitly describes a rewrite or redesign of the system, use rewrite.
Dispatch the context-summarizer agent via the Task tool for the actual document writing. Provide it with:
The agent handles reading conversation context, identifying key files, and writing the document.
references/context-template.md — Document template with YAML frontmatter structure and INDEX.md formatexamples/example-context-doc.md — Complete example of a well-written context document for a user authentication featurenpx claudepluginhub benbentwo/benbentwos-claude-marketplace --plugin context-docsManages per-feature living documents that capture decisions, constraints, and reasoning across AI sessions. Use when starting a feature, resuming work, or making technical decisions.
Creates and manages task documentation including implementation plans, task IDs, and archiving completed work. Useful when starting a new feature or finishing one.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.