feature-list

Reports per-stage status of tracked features as a reverse-date-ordered markdown table.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill feature-list-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-list
Source: https://github.com/cagriy/dev-skills/tree/main/skills/feature-list
Command: npx skills add https://github.com/cagriy/dev-skills --skill feature-list-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple features move through a brainstorm → design → plan → implement pipeline, it becomes hard to remember which features are open, which stage each one reached, and what to do next. This Skill reads the feature trackers, stage files, and git history in the repo and answers that question with a single status table, without ever modifying anything. ## Core Features & Use Cases - Per-stage status table: Shows storm, design, plan, and implement status for every feature under features/, sorted by most recent activity, with a suggested next-step command per row. - In-progress detection: Inspects plan-stage commits on the current git branch to report partially implemented features (e.g. "in progress — Stage 3"). - Read-only and fault-tolerant: Never creates folders, edits trackers, or commits; missing trackers, unparseable timestamps, or absent git repos degrade to fallbacks with a closing note instead of failing. - Use Case: After a week of parallel work, run the skill to see that v7 is mid-implementation at Stage 2, v6 still needs a plan, and v4 is ready to implement — then jump straight to the right command. ## Quick Start Ask the assistant to list the features currently in flight in this repo, optionally including completed ones by passing the argument "all".

Frequently Asked Questions about feature-list

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

FAQPage Schema
How do I see which features are still open in my repo?

Run the feature-list skill with no arguments to list only open features — those whose implementation is not complete. It prints a table showing each feature's storm, design, plan, and implement status plus the next command to run.

How do I list completed features as well as open ones?

Pass the argument "all" to include finished features in the report. Without it, only features with remaining work are shown; "all" is the only accepted argument and anything else stops the skill with an error.

How is in-progress implementation detected without a stage file?

The skill searches the current branch's git log for plan-stage commits matching the feature's version pattern. The highest committed stage number is reported, since implementation resumes at the lowest uncommitted stage.

Does listing features modify the repo or trackers?

No. The skill is strictly read-only: it never creates folders, seeds or edits trackers, writes files, commits, or pushes. It deliberately avoids the feature resolver because that tool mutates the repo as a side effect.

What happens if a feature tracker is missing or out of date?

The skill falls back to filesystem signals — stage markdown files, last commit dates, and file modification times — and flags disagreements between tracker and files with a dagger symbol. Missing data downgrades a cell rather than aborting the report.