feature-manifest

Manage feature manifests mapping feature IDs to implementation files and changelogs.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill feature-manifest-cenredjun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-manifest
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/feature-manifest
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill feature-manifest-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty about which feature owns which parts of the codebase by providing a single source of truth (feature manifests) that link feature IDs to implementation files, tests, dependencies, and changelog entries. It prevents stale or orphaned code, improves release traceability, and makes it easier to validate feature completeness before shipping.

Core Features & Use Cases

  • Manifest creation & updates: Create new feature manifests before implementation and update manifests as files and tests are added or changed.
  • Code-to-feature mapping: Discover which feature owns a file or directory and list all implementation files, entry points, and related tests.
  • Validation & health checks: Run automated manifest validation, detect stale or orphaned features, and surface missing tests or inconsistencies for release readiness.
  • Use case: A developer implementing a new payment flow creates the manifest first, implements code and tests, runs validation and health checks, and appends a changelog entry so release engineers can verify feature completeness.

Quick Start

Ask the assistant to list all features and their implementing files using the repository's feature info and validation scripts so you can identify ownership and health at a glance.

Frequently Asked Questions about feature-manifest

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

FAQPage Schema
How do I map feature IDs to implementation files for release traceability?

To map feature IDs to implementation files for release traceability, you manage feature manifests that link feature IDs to files, tests, dependencies, and changelog entries. This creates a single source of truth for code ownership and release readiness.

How do I detect stale or orphaned code in a manifest-driven workflow?

To detect stale or orphaned code in a manifest-driven workflow, you run automated manifest validation and health checks via npm-based CLI scripts. This surfaces orphaned features, missing tests, and inconsistencies before shipping.

What is a feature manifest and when do I need it for codebase management?

A feature manifest is a single source of truth linking feature IDs to implementation files, tests, dependencies, and changelog entries. You need it when managing code traceability, preventing stale code, and validating feature completeness during release preparation.

Does feature manifest validation work with npm-based CLI scripts?

Yes, feature manifest validation works with npm-based CLI scripts for listing, creating, validating, and health-checking features. It applies to codebases using manifest-driven workflows to satisfy validation, staleness detection, and changelog requirements during development.

What's the best way to ensure feature completeness before shipping a release?

The best way to ensure feature completeness before shipping a release is to create manifests before implementation, update them as files change, run automated validation and health checks, and append changelog entries so release engineers can verify completeness.

How do I discover which feature owns a specific file or directory?

To discover which feature owns a file or directory, you use the repository's feature info scripts to list all features and their implementing files. This code-to-feature mapping identifies ownership and tests at a glance.