Break down vague epics, feature ideas, or product concepts into clear, workable requirements with acceptance criteria — acting as a Business Analyst / Product Owner. Use this skill whenever the user says "define requirements", "break this down", "what are the requirements for", "write requirements", "BA this", or describes a feature/epic they want decomposed into actionable items. Also trigger when the user shares a product idea and asks to make it concrete, says "I want to build X", or needs help turning a vague concept into structured deliverables.
Rewrite and optimize prompts for clarity, structure, and effectiveness. Use this skill whenever the user says "optimize this prompt", "improve my prompt", "rewrite this prompt", "make this prompt better", "structure this prompt", or pastes a rough draft of instructions/prompt they want refined. Also trigger when the user says "prompt engineer this", "clean up this prompt", or asks you to turn a vague idea into a proper prompt.
Create a principal-engineer-level implementation plan from a Jira ticket. Use this skill whenever the user provides a Jira ticket URL (e.g., https://your-org.atlassian.net/browse/TICKET-123), a bare ticket ID (e.g., APKNOWLEDG-640), or says "plan this Jira ticket". Fetches the ticket details first (summary, description, acceptance criteria, comments, linked issues), then challenges the approach, interviews the user, launches parallel agents to explore the codebase and gather context, and produces a comprehensive plan with alternative approaches, risk analysis, detailed testing strategy, observability, and deployment steps.
Create a principal-engineer-level implementation plan from a Notion page. Use this skill whenever the user provides a Notion URL (e.g., https://www.notion.so/...), mentions a Notion page or doc, or says "plan this Notion doc". Fetches the page content first, then challenges the approach, interviews the user, launches parallel agents to explore the codebase and gather context, and produces a comprehensive plan with alternative approaches, risk analysis, detailed testing strategy, observability, and deployment steps.
Create a principal-engineer-level implementation plan for a task, feature, or bug fix from a plain text description or conversation context. Use this skill whenever the user says "plan this", "create a plan", "how should we implement this", or wants to think through implementation before writing code — even if they don't explicitly say "plan". If the user provides a Jira ticket or Notion page, use /hnh-plan-jira or /hnh-plan-notion instead — those fetch the ticket details automatically.
Deep-research a person's online presence and produce a signal-driven intelligence brief through a VC lens — deal flow, funding rounds, M&A, portfolio signals, market thesis, competitive intelligence. Maintains an extensible source registry per profile. Use this skill whenever the user mentions watching someone's profile, tracking a person online, researching someone's social presence, wants to know what someone has been up to, asks 'what is [person] doing lately', or provides a person's name with context suggesting they want a profile deep-dive. Also triggers for 'profile watch', 'track [person]', 'research [person]', 'what has [person] been saying', or 'add source to [person]'.
Deep PR review with context gathering, build verification, and principal-engineer-level code review. Use this skill whenever the user shares a GitHub PR URL, mentions reviewing a PR, asks to check/review/audit a pull request, or says "review this PR". Triggers on PR URLs from github.com, PR numbers with repo context, or any request to review code changes in a pull request — even if the user doesn't explicitly say "review".
Wrap up a coding session into a pull request — commit changes, create a branch, push, open a PR with a human-readable description, self-review with /hnh-review-pr, fix findings, and post the outcome. Use this skill whenever the user says "create a PR", "wrap this up", "open a PR", "submit a PR", "make a pull request", "send this for review", or wants to turn their current work into a PR. Also trigger when the user finishes implementing a feature/fix and says something like "let's get this merged", "ready for review", or "push this up". This skill handles the entire PR lifecycle from uncommitted changes to a review-ready pull request.