Menu
Turn a feature passport into customer-facing release notes — headline, what shipped, what changes in the customer's workflow, links.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review a PRD against Kalina's seven review criteria. For each criterion, flag specific lines that pass or fail with line numbers and push back with a concrete question. Output goes to reviews/{prd-name}-review-{date}.md.
Walk a PM through writing a PRD against the generic template, asking one question per section and drafting based on the answer. Pulls evidence from a finding doc as it goes.
Walk through a PRD from an engineering lead's lens, surfacing implementation ambiguities and missing technical requirements. Uses the AskUserQuestion tool to interview the PM one question at a time, then writes the resolved answers into the PRD as a clarifying-questions appendix.
Pull Modjo call summaries and full transcripts for a date range and topic, structured for downstream investigation.
| name | release-notes |
| description | Turn a feature passport into customer-facing release notes — headline, what shipped, what changes in the customer's workflow, links. |
| when-to-use | When a feature is shipping and you need to draft customer-facing release comms from the passport. Output is markdown plus a tweet-length headline. |
@passports/quote-vitals.md)professional | playful | technical). Defaults to professional.Read the passport. Extract:
Draft a markdown file at release-notes/{feature-slug}-{date}.md with sections:
Generate-type skill — produces customer-facing copy from internal context. Reusable for any feature. The passport is the source of truth; the release note is its public-facing shape.