feature-status-sync

Name: feature-status-sync
Availability: InStock
Author: Buddypia

Synchronize feature status by verifying code and test files against CONTEXT.json.

Updated Feb 21, 2026

Search Tags:#automation #project management #documentation #code sync #status update #feature management

Ready to run

npx skills add https://github.com/buddypia/kaiju-voice --skill feature-status-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-status-sync
Source: https://github.com/buddypia/kaiju-voice/tree/main/.claude/skills/feature-status-sync
Command: npx skills add https://github.com/buddypia/kaiju-voice --skill feature-status-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your project's documentation and code status are always in perfect alignment, preventing outdated information and streamlining development workflows.

Core Features & Use Cases

Automated Status Updates: Verifies code and test file existence against your CONTEXT.json to automatically update feature progress.
Index File Generation: Recreates index.md files for individual features and the top-level registry, ensuring a consistent project overview.
Use Case: After a developer completes a feature, this Skill automatically checks if the corresponding code and tests are present, updates the CONTEXT.json progress, and regenerates the feature's index.md to reflect the new status.

Quick Start

Run the feature status sync skill to update the project's documentation and code status.

Frequently Asked Questions about feature-status-sync

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

FAQPage Schema

How do I keep project documentation and code status in sync automatically?▼

To keep project documentation and code status in sync, this Skill verifies code and test file existence against a central CONTEXT.json single source of truth, automatically updating feature progress and regenerating index.md files to reflect the validated status changes.

What is the best way to automate feature status updates across a project registry?▼

The best way to automate feature status updates is to verify file existence against CONTEXT.json, log status transitions for auditability, and automatically generate top-level feature-registry.json and index.md files to ensure a comprehensive project overview.

Do I need a CONTEXT.json file to synchronize feature progress and documentation?▼

Yes, you need a CONTEXT.json file to synchronize feature progress because it acts as the single source of truth that the Skill checks against to verify code and test file existence before updating documentation and logging status history.

How does generating index.md files from a central registry improve project management?▼

Generating index.md files from a central registry improves project management by recreating individual feature documentation and a top-level overview, ensuring developers have a consistent, updated view of feature progress and code alignment without manual tracking.

Can I track feature status history and audit transitions using automated documentation sync?▼

Yes, you can track feature status history and audit transitions because the documentation sync process logs status transitions and history against the CONTEXT.json single source of truth, providing a clear audit trail of development progress.