feature-catalog

Manage project-local SQLite3 feature records, file mappings, and architectural decisions.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/thistleknot/skills --skill feature-catalog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-catalog
Source: https://github.com/thistleknot/skills/tree/main/feature-catalog
Command: npx skills add https://github.com/thistleknot/skills --skill feature-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature drift and scattered project knowledge happen when implemented capabilities, their file mappings, and architectural decisions live only in loose notes; this Skill centralizes them in a queryable project-local SQLite3 catalog.

Core Features & Use Cases

  • Project-local SQLite feature registry: Store features, statuses, priorities, and long-form rationale in a structured schema at the repo root.
  • File-to-feature mapping: Maintain a join table that answers which files a feature touches and which features affect a given file.
  • Architectural decision capture: Record before/after state and measured impact for traceable engineering change history.
  • Supports incremental updates: Use idempotent upsert patterns and stable feature IDs to safely re-run updates over time.

Quick Start

Create or update FEATURE_CATALOG.sqlite3 by running the Setup and Upsert logic so features and their associated file mappings are persisted in the local SQLite database.

Frequently Asked Questions about feature-catalog

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

FAQPage Schema
How do I track implemented features and file mappings in a local database?▼

Track implemented features in a local database by using a project-local SQLite3 feature catalog to store features, file mappings, and architectural decisions in structured tables. This replaces scattered documentation with a queryable schema at the repo root.

What's the best way to centralize architectural decisions and feature statuses?▼

Centralize architectural decisions and feature statuses by recording before, after, and measured impact states in a local SQLite3 database. This captures traceable engineering change history alongside feature priorities and long-form rationale.

How do I map which files a feature touches using SQLite?▼

Map which files a feature touches by maintaining a feature_files join table in your SQLite3 database. This table answers both which files a feature affects and which features modify a given file.

Can I safely re-run feature updates without duplicating records?▼

You can safely re-run feature updates without duplicating records by applying idempotent upsert patterns and stable feature IDs. This allows incremental catalog updates over time without creating duplicate database entries.

Do I need external dependencies to manage a feature catalog with SQLite3?▼

You do not need external dependencies to manage a feature catalog. The system requires only the standard library sqlite3 module to create and query the database tables at your project root.

When should I use a SQLite feature registry instead of loose notes?▼

Use a SQLite feature registry instead of loose notes when feature drift and scattered project knowledge become problematic. A centralized catalog becomes necessary when multiple agentic coding workflows need to query implemented capabilities and file ownership.