context-manager

Aggregates project documents into task context summaries with risk detection.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/fen-zx/NovelToScript --skill context-manager-fen-zx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-manager
Source: https://github.com/fen-zx/NovelToScript/tree/main/.agents/skills/content-manager
Command: npx skills add https://github.com/fen-zx/NovelToScript --skill context-manager-fen-zx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In long-running AI-assisted development projects, the AI forgets prior requirements, decisions, and changes across sessions, leading to duplicated work, conflicting implementations, and repeated mistakes. This Skill builds a unified project memory so every downstream Skill starts with full historical context. ## Core Features & Use Cases - Project Memory Aggregation: Automatically reads PRD.md, DESIGN.md, PAGE_SPECS.md, DECISIONS.md, CHANGELOG.md, PROJECT_STATE.md, API_SPECS.md, and TASKS.md to build a task-relevant context summary. - Conflict & Risk Detection: Identifies duplicate development, decision conflicts (e.g., Redux vs Pinia), state conflicts, and API inconsistencies before code generation begins. - Context Compression: When project documentation exceeds 100 pages, generates a condensed Context Summary covering tech stack, page/component/API counts, and recent activity. - Use Case: Before asking an AI to add a batch-delete feature to a user management page, run this Skill to surface existing components (UserTable, SearchForm), existing APIs, the prior server-side pagination decision, and the risk that the batch-delete endpoint does not yet exist. ## Quick Start Ask the AI to run the context manager with your task description, such as "add batch delete to the user management page", before any code generation begins.

Frequently Asked Questions about context-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AI from forgetting project history across sessions?▼

Run the context manager before every development task. It reads PRD, design, decisions, changelog, and project state documents, then generates a task-specific context summary so the AI retains historical decisions and prior changes.

How to detect duplicate components before generating new code?▼

The context manager indexes existing pages, components, and APIs from project documents and flags when a requested component or page already exists. It prioritizes reuse of existing components over generating new ones.

What documents does the context manager read by default?▼

It reads PRD.md, DESIGN.md, PAGE_SPECS.md, DECISIONS.md, CHANGELOG.md, PROJECT_STATE.md, API_SPECS.md, and TASKS.md from the project directory. These files provide requirements, decisions, changes, and current implementation status.

Does the context manager work with large projects over 100 pages of documentation?▼

Yes. When documentation exceeds 100 pages, it automatically generates a compressed Context Summary containing the tech stack, page and component counts, recent decisions, and recent changes to keep context length manageable.

What input formats does the context manager accept?▼

It accepts natural language task descriptions such as "add batch delete to the user management page" or structured JSON with a task field. Both formats produce a Markdown context summary with risk warnings.

When should the context manager not be skipped in a workflow?▼

It must run before requirement analysis, design generation, component generation, page generation, API integration, test generation, and code review Skills. Skipping it risks decision conflicts, repeated development, and API inconsistencies.