Skip to content
Back to skills

Product Status

ASecurity

Render a read-only dashboard of the Product/ folder — stage/gate completion, risk-burndown state, feature counts by classification and priority, the ranked innovation edge list, and gaps (UVP elements with no feature, features missing acceptance criteria, unclassified features). Use to review progress or spot holes.

  • 4 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
ai-agents

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add InSciCo/i-framework --skill product-status --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Product Status?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Product Status
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/inscico-product-status/badge)](https://www.skillsdirectory.com/skills/inscico-product-status)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: product-status
description: Render a read-only dashboard of the Product/ folder — stage/gate completion, risk-burndown state, feature counts by classification and priority, the ranked innovation edge list, and gaps (UVP elements with no feature, features missing acceptance criteria, unclassified features). Use to review progress or spot holes.
allowed-tools: Read, Glob, Grep
---

# /product-status — the dashboard (read-only)

You summarize the whole `Product/` folder at a glance. Never modify files — if you find problems, list them as gaps for the founder to fix with the relevant skill.

## Procedure

1. **Read everything.** The three stage artifacts (and their `gate:` frontmatter), `Product/Features/F*.md` (frontmatter + body), `Product/features-index.md` if present, and `Product/competition.md` if present.

2. **Compute:**
   - **Stage/gate completion** — which of the three gates are passed vs. open (the risk-burndown line).
   - **Feature counts** — total, by `classification`, by `priority` (MoSCoW), by `status`.
   - **Innovation edge list** — innovation features sorted by `innovation_weight` desc, each with its `contributes_to` UVP.
   - **Weight distribution** — are weights spread or clustered?

3. **Run integrity checks** (the high-value part) — validate cross-file consistency and list every violation:
   - **Dangling UVP reference:** a feature's `contributes_to` value that matches no UVP id in `innovation.md`.
   - **UVP orphan:** a UVP element in `innovation.md` with no innovation feature tracing to it.
   - **Classification/weight mismatch:** implementation with weight ≠ 0; innovation with weight 0; innovation missing `contributes_to`.
   - **Thin feature:** missing a user-story clause, or **<3 acceptance criteria**.
   - **Broken dependency:** a `depends_on` id that points to no existing feature.
   - **Portfolio flags:** apply the same thresholds as `/classify` — >40% innovation; and, *only when there are ≥3 innovation features*, innovation weight span <30 points (skip the spread check below that count).
   - **Cherry-picked matrix:** if `competition.md` exists and the "Us" column is ✓ on every row, flag it — a credible comparison has ≥1 row where a rival matches or beats us.
   - **Unverified competitor claims:** if `competition.md` exists, count cells marked `?` and surface them as items to verify (with the snapshot date).

4. **Render** a concise dashboard — a risk-burndown header, a counts table, the ranked edge list, and a clearly separated **Gaps / next actions** section that names which skill fixes each gap (`/feature`, `/classify`, `/innovate`).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.