featuring

Solid

Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tree-sitting (structural) with semantic (why/what-for) layer.

Data & Documents 150 stars 6 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
73
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Featuring Generate `_FEATURES.md` files — top-down documentation of what a codebase **does**, organized by feature/capability, anchored to specific source symbols. **tree-sitting** tells you WHAT symbols exist. **_FEATURES.md** tells you WHY they exist and what they accomplish together. For large codebases, the root `_FEATURES.md` decomposes into sub-feature files linked by capability area — not by folder structure. An agent starts at the root and is drawn into sub-files only when working on a relevant area. ## Dependency Requires **tree-sitting** skill. Uses its engine for AST scanning. ```bash uv venv /home/claude/.venv 2>/dev/null uv pip install tree-sitter-language-pack --python /home/claude/.venv/bin/python ``` tree-sitting caches its scan to `/tmp/treesit-cache`, keyed by repo path plus skip set. That cache persists symbols and imports but NOT file source, so a cache HIT returns `source=None`. `gather.py` re-reads those files from disk; do not assume `entry.source` is populated if you write against the engine directly. (Before this was handled, gather crashed on its second run against a repo while the first succeeded — diagnosed 2026-08-22.) For quick structural orientation before running gather.py, use tree-sitting's CLI: ```bash TREESIT=/mnt/skills/user/tree-sitting/scripts/treesit.py # Complete tree, sparse detail — see the full shape /home/claude/.venv/bin/python $TREESIT /path/to/repo --depth=-1 --detail=sparse ``` ## Workflow: Multi-Pass Synthesis Fe...

Details

Author
oaustegard
Repository
oaustegard/claude-skills
Created
11 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

to-features

Generate FEATURES.md at the repo root by reading CONTEXT.md and docs/adr/, then enumerating the user-facing features the domain implies. Use after /grill-with-docs has settled the domain language and before /to-prd writes per-feature specs. Bridges the product→engineering gap between domain understanding and feature specification — the missing step that mattpocock's chain doesn't cover natively.

3 Updated 6 days ago
soulmachine
Data & Documents Listed

doc-feature

Generate feature/module documentation after implementation. Covers business context (why, for whom, use cases), technical architecture (data flow, API, decisions), and operational details (limitations, edge cases). Integrates with the SSOT structure (docs/DOCUMENTATION_STRATEGY.md). USE WHEN: after >3 new files or a feature change. Triggers: "document this feature", "update docs/features", "doc-feature", "sync docs ↔ code", «задокументируй фичу», «обнови docs/features».

0 Updated 2 months ago
akuroglo
Web & Frontend Listed

hyperbuild-4-5-feature-specs

Step 4.5 of the hyperbuild pipeline — expands every must/should PRD feature into its own deep spec file at the repo root: features/NN-<slug>.md (frontmatter id, name, moscow, status: specced, screens; eight required body sections) plus the features/00-index.md roster. Cap 15 files (standard) / 25 (premier). Spawns 3–5 hb-feature-author subagents in parallel, features split into batches, every claim evidenced from the research vault. Steps 6–8 draw real flows and content from these specs, step 11 tasks cite feature ids, and the step 12 and 16 gates check feature coverage and status flips. Invoked by the hyperbuild router via Skill(); not run directly by users.

0 Updated 2 months ago
zakariaf