review-features

Aggregate cross-feature progress data into markdown and JSON reports.

21|4|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/JotJunior/cstk --skill review-features
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-features
Source: https://github.com/JotJunior/cstk/tree/main/global/skills/review-features
Command: npx skills add https://github.com/JotJunior/cstk --skill review-features

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cross-feature portfolio analysis to track and compare progress across all feature domains, enabling teams to quickly identify gaps and decide on archiving, abandoning, prioritizing, or continuing work.

Core Features & Use Cases

  • Cross-feature aggregation: scans docs/specs//tasks.md and docs/features// to build a portfolio view.
  • Progress, risk and priorities: computes completion percentages, pending/blocked tasks, and criticality to guide actions.
  • Actionable recommendations: suggests archiving, abandoning, prioritizing, or continuing based on evidence.

Quick Start

Run the aggregation script to generate the cross-feature report.

Frequently Asked Questions about review-features

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

FAQPage Schema
How do I aggregate cross-feature progress data into a portfolio dashboard?

Cross-feature portfolio dashboards are generated by scanning docs/specs/*/tasks.md and docs/features/*/tasks.md directories to compute completion percentages, criticality, and task statuses. The aggregation script outputs a human-readable markdown table and machine-friendly JSON-lines for pipelines.

What's the best way to compare feature progress across multiple project directories?

Comparing feature progress across directories requires parsing specs to extract descriptions, statuses, and subtasks from tasks.md files. This cross-feature aggregation computes pending and blocked tasks to surface actionable insights for portfolio-level decisions.

Can I get machine-readable JSON output from feature portfolio reporting?

Feature portfolio reporting supports machine-friendly JSON-lines output suitable for downstream pipelines. The aggregation script produces both a markdown table for human review and JSON-lines containing computed completion percentages and criticality data.

How does cross-feature task parsing identify which features to prioritize or abandon?

Cross-feature task parsing identifies features to prioritize or abandon by computing completion percentages, pending tasks, blocked tasks, and criticality from specs. Based on this evidence, it suggests archiving, abandoning, prioritizing, or continuing work across the portfolio.

Do I need any external dependencies to generate cross-feature portfolio reports?

Generating cross-feature portfolio reports requires no external dependencies. The aggregation script operates directly on local docs/specs/*/tasks.md and docs/features/*/tasks.md files to extract descriptions, statuses, and subtasks for portfolio analysis.

What file structure is required for cross-feature portfolio aggregation?

Cross-feature portfolio aggregation requires tasks.md files organized within docs/specs/*/ and docs/features/*/ directories. The script reads these specs to extract descriptions, statuses, and subtasks, computing completion percentages and criticality for the portfolio view.