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
npx -y skills add InSciCo/i-framework --skill product-statusAssembled 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.mdif present, andProduct/competition.mdif present. -
Compute:
- Stage/gate completion — which of the three gates are passed vs. open (the risk-burndown line).
- Feature counts — total, by
classification, bypriority(MoSCoW), bystatus. - Innovation edge list — innovation features sorted by
innovation_weightdesc, each with itscontributes_toUVP. - 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_tovalue that matches no UVP id ininnovation.md. - UVP orphan: a UVP element in
innovation.mdwith 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_onid 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.mdexists 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.mdexists, count cells marked?and surface them as items to verify (with the snapshot date).
- Dangling UVP reference: a feature's
-
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.