nurijanian-skills

Review existing requirements or convert raw context into requirements that meet 18 quality characteristics (unambiguous, clear, cohesive, consistent, conformant, current, modifiable, traceable, relevant, unique, categorised, complete, correct, concise, testable, implementation-independent, owned, feasible). Use whenever the user mentions requirements, PRDs, specs, user stories, acceptance criteria, requirements review, requirements audit, BRD, FRD, requirements quality, requirements catalogue, requirements traceability, "are my requirements any good", "turn this into requirements", "make these requirements better", or shares meeting notes, interview transcripts, stakeholder input, or feature ideas that need to be formalised. Trigger even when the user does not use the word "requirement" if the artifact they share is functionally a requirement (e.g., "the system should let users export to PDF", "we need a way for admins to revoke access").

Find, diagnose, and fix misalignment in corporate settings. Use this skill when teams are stuck, decisions aren't being made, meetings are dysfunctional, or there's confusion about who has authority. Trigger on: "we're misaligned", "can't get everyone on the same page", "meetings are a waste of time", "who's supposed to decide this?", "too many cooks", "analysis paralysis", "nothing gets decided", "people aren't following the process", or any time group dynamics are blocking progress.

Represent messy work as durable obligations, workflow building blocks, fragments, AI/automation insertion points, and exception queues. Use this whenever the user wants to analyze interviews, messy notes, customer research, operational workflows, PM workflows, vertical SaaS opportunities, AI insertion points, automation opportunities, "durable obligations", fragmented work, hated execution burden, or where AI should fit into an existing workflow. This skill is primarily a thinking and workflow-mapping tool, not a startup idea generator.

PM stress-test roleplay. Use this skill whenever a PM wants to practice handling a difficult situation with a designer or engineer, stress-test their instincts in a realistic scenario, or understand what it feels like to be on their team when things go wrong. You play a frustrated, skeptical, or overloaded team member and respond as they would. Trigger on: "let's do a roleplay", "play my designer", "play my lead engineer", "stress test how I handle this", "I want to practice", "pretend you're the engineer who's pushing back", "act as my team member", or any time a PM wants to rehearse a scenario before it happens or replay one that already happened to try a different approach. Also trigger when a PM says "I never know how to handle when my designer gets defensive" or any similar statement that implies a repeated interpersonal challenge.

PM blind spot identifier. Use this skill whenever a PM wants a comprehensive read on which behavioral gaps they have that they can't see themselves. This is the deepest and most comprehensive mode — a full interview that surfaces systematic patterns across all 7 behavioral clusters. Trigger on: "what are my blind spots?", "what am I missing as a PM?", "give me an honest full assessment", "I want a comprehensive read on where I fall short", "test me across everything", "what do I consistently get wrong?", "I want to know what I'm not seeing about myself", or any time a PM wants a thorough behavioral audit that goes beyond a single situation or decision. Also trigger at the end of another mode when a pattern has emerged across multiple interactions and the PM wants to go deeper.

PM decision quality auditor. Use this skill whenever a PM wants to audit a specific decision they made — not just whether it worked out, but whether it was a *good decision* by the criteria that define PM excellence. Trigger on: "was this the right call?", "I want to audit this decision", "I'm not sure I made this well", "help me think through whether this was a good PM decision", "I made a call about X and I want to pressure-test it", "I cut this feature / changed this priority / chose this direction — was that right?", or any time a PM wants structured feedback on the quality of a specific decision they made, regardless of whether it turned out well. Important: good outcomes don't make good decisions; bad outcomes don't make bad decisions. This skill audits the *process*, not the result.

PM alignment coach and router. Use this skill whenever a product manager (or someone managing products) wants to reflect on their own performance, check their behaviors against a standard of excellence, get coaching, practice a difficult scenario, audit a decision, or understand their blind spots. Trigger on phrases like: "am I being a good PM?", "check how I'm doing", "coach me", "how would my team see me?", "let's roleplay a scenario", "audit my decision", "what am I missing as a PM", "what are my blind spots", "test me as a PM", "I want to improve as a PM", or any time a PM is reflecting on their own practice. Also trigger when someone mentions PM self-improvement, PM development, or wanting to think through how they handled a team situation.

PM behavioral retrospective. Use this skill whenever a PM wants to debrief a specific situation they recently handled — a meeting, a conflict, a decision, a conversation with an engineer or designer, a feature that shipped badly, a standup that went sideways. The PM describes what happened and you map their actual behavior against the PM excellence framework to surface what they did well and where they fell short. Trigger on: "I just had a situation where...", "I want to think through how I handled...", "something happened this week that I want to debrief", "was this the right call?", "I'm not sure I handled this well", or any time a PM describes a specific recent event and wants feedback on their behavior.

Outside-in PM perspective generator. Use this skill whenever a PM wants to know how they're actually landing with their team — specifically with designers and engineers. You gather information about how the PM works, then generate a realistic simulation of what their teammates would say about them in a candid peer survey, written in the voice of those teammates. Trigger on: "how does my team see me?", "what would my team say about me?", "do I come across as...", "I wonder if my team thinks I...", "what's my reputation with the engineers?", "would a designer say I'm a good PM?", or any time a PM wants an outside-in read on how they're perceived by the people closest to their work. Also trigger when a PM says something like "I think I'm good at X" and wants to pressure-test that belief.

This skill should be used when a user wants to identify which parts of a codebase are safe to modify with AI ("vibe code") and which require careful human engineering. It classifies files and modules into Leaf (safe to vibe), Branch (caution), or Trunk (hands off) based on dependency isolation, stability, and external verifiability. Use when users say "find safe places to vibe code", "where can I let AI loose in this repo", "leaf nodes", "vibe-code audit", "can a PM edit this codebase", or when someone points at a directory and asks whether it's safe to let Claude rewrite it. Grounded in Erik Schluntz's (Anthropic) "leaf nodes vs trunks" framework from the "Vibe coding in prod" talk.

Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation.

Analyze technology announcements to surface non-obvious strategic implications using Verbalized Sampling. Works against any context: a business, product, codebase, feature branch, personal project, career, or exploratory domain. Use when a new technology, feature, or capability is announced and you want to understand what new outcomes, affordances, and competitive levers it creates — beyond the obvious hot takes. Triggers on: "analyze this announcement", "what does this mean for us", "tech sensemaking", "new feature dropped", "what can we do with this", "sensemaking on this", "strategic implications of", or any request to evaluate a technology change strategically. Category: Product Strategy

This skill should be used when someone needs to find, propose, or evaluate a focal point in a coordination, negotiation, or alignment problem. A focal point is a solution that people converge on without explicit agreement — because it is uniquely prominent, simple, or recognizable. Based on Thomas Schelling's "The Strategy of Conflict." Triggers on "where should we align?", "how do we get everyone on the same page?", "what's the obvious choice?", "find a focal point", "Schelling point", "coordination problem", "how do we agree without talking?", "what would everyone pick?", "propose a standard", "set a default", or any situation where multiple parties need to converge on a single choice without full communication.

Generate diverse outputs by prompting for a probability distribution instead of a single response. Implements Verbalized Sampling (VS) from Zhang et al. 2025 — a training-free technique that counteracts LLM mode collapse caused by typicality bias in alignment data. Use when the task needs genuine diversity: creative writing, brainstorming/ideation, synthetic data generation, persona/dialogue simulation, adversarial examples, open-ended QA with multiple valid answers, or any situation where "generate 5 ideas" keeps returning the same cluster. Do NOT use for: single correct answer tasks, factual lookup, strict format compliance.