Product status

Skill InSciCo/i-framework/.claude/skills/product-status

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.From its SKILL.md

Install

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 538 tokens by cl100k_base, as published. Nobody here has run it

/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

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.
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?
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).
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).

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product growth skills give in 538 tokens

Counted across 694 of the 879 authors here whose files we hold, read 2026-09-06

Check for product marketing context firstin 49 of 694, across 20 files
Validate the why before building featuresin 18 of 694, across 4 files
Respond to every comment in real-timein 17 of 694, across 6 files
Structure launch marketing across three channel typesin 16 of 694, across 4 files
Recruit early users one-on-onein 13 of 694, across 2 files
Ask one question at a timein 13 of 694
Rank features using ICE scoringin 12 of 694, across 3 files
Identify primary conversion goalin 11 of 694, across 3 files
Identify traffic contextin 11 of 694, across 3 files
Evaluate headline effectivenessin 11 of 694, across 3 files
Check visual hierarchy and scannabilityin 11 of 694, across 3 files
Run product diagnosticsin 11 of 694, across 3 files

Said here and by no other author read

Compute stage and gate completion states
Compute feature counts by metrics
Compute the innovation edge list
Run integrity and consistency checks
Render a concise dashboard

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.