hamza-ali-shahjahan /kill-or-keep
Usage: /kill-or-keep (run quarterly, end of quarter)
What this does
Invokes agents/portfolio/kill-or-double-down/. Produces a full portfolio review document at brain/decision-log/portfolio-review-YYYY-QN.md.
What you do as the assistant
- Confirm with user: "this is a quarterly review and will force verdicts. Proceed?"
- Read all products'
product.config.json,metrics.md, last 90 days ofdecisions/. - Pull current metrics via telemetry-aggregator.
- Ask user: "estimated hours per week on each product over last quarter" — fill in.
- Generate the review per the agent's output spec.
- For each KILL verdict, generate the sunset plan in full.
- Save to file. Print summary in chat.
7b. Factory curator pass (rides here quarterly — v2.20 MECE curator, now measured):
run
bun run skill-report --days 90.dormantskills are archive candidates (factory/skills/_archive/— archive, never delete),demotedskills get a look before anything trusts them, and guard-sunset questions citebun run defect reportcounts. Record pin / consolidate / archive per the skill-authoring playbook's curator rules. - Update each killed product's
product.config.json→status: "sunset_planned"+sunset_date: <T+60>. - Add an entry to
MEMORY.mdif portfolio-level patterns emerged.
Warning
This skill produces uncomfortable decisions. Don't soften the verdicts. The whole point is the forcing function.