pruthivim

@pruthivim source repo

4 skills
0 followers
20 hours ago last updated

▌
Prd Critic · pruthivim bundle
Adversarial review of PRDs, specs, and requirements docs — plays a skeptical Lead PM / Principal Engineer / Senior QA reviewer who hunts for missing acceptance criteria, undefined success metrics, unhandled edge cases, scope creep, missing technical/operational constraints, unstated assumptions, ownership gaps, weak problem framing, and missing telemetry. Use this any time the user shares, pastes, or uploads a PRD, spec, or requirements doc and asks for feedback, a review, or a critique — and also proactively whenever someone is drafting a PRD in-chat and asks something like "does this look good?", "is this ready?", or "what am I missing?". Trigger even if they don't say "PRD" explicitly — "requirements doc", "spec", "one-pager for eng", and "feature doc" all count. Produces both an annotated copy of the document AND a standalone gap report.

0
installs
▌
Rice Scorer · pruthivim bundle
Scores and prioritizes a backlog of features, ideas, or initiatives using the RICE framework (Reach, Impact, Confidence, Effort), producing a ranked table with a calculated score and a justification for every input. Use this whenever the user wants to prioritize a backlog, compare feature ideas, decide what to build next, rank initiatives, or mentions RICE, Reach/Impact/Confidence/Effort, or "prioritization score," even if they only paste a rough list of ideas and don't ask for RICE by name. Also trigger when a user asks "what should we build first" or shares a roadmap/backlog and wants it ranked objectively.

0
installs
▌
Insight Processor · pruthivim bundle
Turns raw user research into a structured insight matrix mapping user statements to problem statements. Reads interview transcripts, call recording transcripts, written call notes, or survey verbatims and distills them into themes, problem statements, verbatim quotes, severity, and frequency — instead of manual tagging in a spreadsheet. Use whenever the user uploads or references interview transcripts, call notes, user interviews, customer feedback, or qualitative research, or asks to "synthesize," "find themes in," "pull insights from," "tag," "code," or "make sense of" research data — even without saying "insight matrix." Also use for casual phrasings like "what are customers complaining about" or "what's coming up across these calls," or requests to find pain points, recurring complaints, or unexpected/workaround user behaviors. Handles a single transcript or a batch from the same project, offering a combined cross-interview matrix once each is processed.

0
installs
▌
Problem Clarity Check · pruthivim bundle
Evaluates whether a problem statement is genuinely well-defined before solutioning begins, catching cases where a PRD or spec would be built on a premise that's actually a disguised solution, an unvalidated assumption, or a vague target user. Proactively use this before writing a PRD, spec, or feature doc for any problem statement, user pain point, feature request, or "we should build X" idea that hasn't already been through this check — even if the user doesn't ask for it by name. Do NOT use for casual code requests, bug fixes, or small technical asks with no PRD/spec involved; those should proceed unblocked. Can also be invoked explicitly, e.g. "run a problem clarity check," "sanity check this problem statement," "is this problem well-defined," or "stress-test this premise."

0
installs

4 published skills