context-updater

Updates project context documents with decisions, changelogs, and task completion records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In multi-iteration AI-assisted development projects, context documents like decision logs, changelogs, and project state files quickly become stale, causing agents and developers to work from outdated information. This Skill automates the write-back of task completion results into all relevant project context documents. ## Core Features & Use Cases - Multi-document synchronization: Updates DECISIONS.md, CHANGELOG.md, PROJECT_STATE.md, TASKS.md, PAGE_SPECS.md, COMPONENTS.md, and API_SPECS.md from a single structured JSON input. - Structured decision recording: Captures decision context, alternatives considered, chosen option, rationale, author, and date in a consistent Markdown format. - Status tracking: Marks pages, components, APIs, and tasks as complete so downstream context retrieval always reflects the latest project state. - Use Case: After finishing a batch-delete feature for a user management page, submit the task completion JSON and have the changelog, decision log, project state, and task list all updated consistently in one pass. ## Quick Start Provide the task completion details as JSON including task name, status, modified components, pages, APIs, decisions, author, and date, then ask the agent to update all project context documents.

Frequently Asked Questions about context-updater

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

FAQPage Schema
How do I keep project context documents updated after each development task?▼

Submit a structured JSON describing the completed task, modified components, pages, APIs, and any new decisions. The Skill updates the changelog, decision log, project state, and task list documents in one consistent pass.

What input format does the context update workflow require?▼

It requires a JSON object with fields for task name, status, modified components, pages, APIs, new decisions with context and rationale, change descriptions, author, and date. Missing fields may result in incomplete document updates.

Which project documents get updated after a task completes?▼

The workflow updates DECISIONS.md, CHANGELOG.md, PROJECT_STATE.md, TASKS.md, and conditionally PAGE_SPECS.md, COMPONENTS.md, and API_SPECS.md when pages, components, or interfaces were added or modified.

Can context updates overwrite previous decisions or task records?▼

The Skill appends records by date rather than overwriting history, and its risk guidelines explicitly warn against covering unrelated old tasks or conflicting decisions. Historical entries are preserved as an audit trail.

When should I trigger a context document update?▼

Trigger it after completing a page, finishing or modifying a component, completing API integration, delivering a low-fidelity prototype, or finalizing any decision, change, or iteration task.