Results for “pr”

Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.

Personal working rules, decision frameworks, and preferences for ejarbe. Invoke with /rules to surface these during any session. AUTO-TRIGGER when working with MCP servers, MCP transport, SSE, streamable HTTP, server migration, .well-known metadata, or MCP server discovery/registration.

Conduct structured, multi-session brand identity interviews to produce a master brandbook covering purpose, positioning, audience, personality, voice, narrative, and founder-brand tension.

Clusters a GitHub issue backlog by root cause into plan-master issues, redirects children with a standardized comment, and bundles architectural-fix PRs that close clusters atomically.

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

Orchestrate a full theory-first idea discovery pipeline. Use when the user wants the analysis counterpart of idea-discovery: literature context, proof-oriented idea generation, novelty checking, DeepSeek critique, and an analysis plan instead of an experiment-first workflow.

Checks how well a Linear cycle is prepared. Reports per-person load in working days against available days, tickets with no estimate, tickets nobody is assigned to, oversized tickets that need splitting, work that did not finish last cycle, on-call rotation cost, and how groomed the backlog behind the cycle is. Invoke when the user says "cyclotic", "cyclotic prep", "cyclotic prep next", "cyclotic review", "cyclotic init", "cyclotic configure", "cyclotic for" a person's name, "cyclotic show cards", "cyclotic list tickets", "cyclotic explain" a person's name, or adds "-v" or "verbose" to any of those. Also invoke when the user asks whether a cycle or sprint is ready, who is over or under capacity, what carried over from last cycle, which tickets still need estimates, how the backlog looks going into planning, what is in the cycle and at what sizes, or how one person's load adds up. Read-only against Linear.

Guides agents through the full lifecycle of NeMo-RL experiments: understanding recipes, launching reproducible runs, analyzing results, and preserving human oversight with git and TSV logs.

Produces a comprehensive, executable 12-month marketing plan structured by AARRR, customized to budget, team, and stage, with cross-references to marketing ideas and current-state audit.

Shape, bet, and build products using the 37signals philosophy from Getting Real, Rework, and Shape Up — fix time, flex scope, and ship with small autonomous teams.

Diagnose which organic growth path to pursue by identifying where the growth constraint lives, using a fast triage based on the McKinsey Growth Pyramid.

Decode an incoming message into a structured breakdown that separates the literal ask from the job-to-be-done, before replying to a loaded Slack ping, email, mandate, or escalation.

Writes or updates pathway pages for Alan Hirsch's platform, following a 12-section architecture that grounds frameworks in Scripture and story, offers practices, and invites course-based formation.

Create and maintain AI-agent integration files for Pump.fun SDK work, including AGENTS/CLAUDE/COPILOT/GEMINI instructions, .well-known discovery, LLM context docs, skills registries, MCP prompts, and terminal rules. Use when wiring agents to Pump.fun development workflows.

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

Automatically maintain skill library consistency whenever a structural change occurs — new skill added, skill renamed, skill deprecated, call graph rewired, or category changed. Updates SKILL-INDEX.md, AGENTS.md, README.md, skill graph, docs/prd/PRD.md, and docs/architecture.md. Load when universal-skill-creator finishes creating a skill, split-skill extracts a child, deprecate-skill retires a skill, improve-skills makes a structural change, or the user manually renames or restructures skills. Also triggers on "update the skill index", "sync skill references", "refresh the skill graph", "fix broken skill cross-references", or "update docs after skill change".

Correlates OT asset inventory with ICS-CERT advisories and CVE data to identify, prioritize, and track vulnerabilities in operational technology environments using Claroty xDome.

Diagnose the PM-to-Director transition using altitude (scope) and horizon (time) axes, identify transition zones, and apply the Cascading Context Map when organizational direction is vague.

Breaks a plan, spec, PRD, or conversation into independently-grabbable GitHub issues using tracer-bullet vertical slices, then publishes them as native sub-issues under a parent tracking issue via the gh CLI.

Daily inbound freelance-job discovery across the markets and platforms the brand chose — scrapes job posts via Claude in Chrome (Freelancer.com API where available), scores each for service fit, deduplicates, and drops matches into a Notion opportunities DB. Runs daily on cron schedule.

Set a deliberate visual direction before any UI is built — the single biggest lever against generic AI output. Derives a posture from product-soul/PRD/specs, scores a curated archetype palette, then generates 2-3 GENUINELY DISTINCT directions and compares them side-by-side before committing to one. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, explore visual options, says "what should this look like", "make it feel like [Linear/Apple/ Duolingo]", "give me design directions", "explore some looks", or when frontend-design routes here. Replaces design-archetype. Sub-skill of frontend-design.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria, focusing on user situations and outcomes for JTBD-style backlog items.

Write and refine user stories using INVEST criteria, the 'As a X, I want Y, so that Z' format, Gherkin acceptance criteria, definition of ready, anti-patterns, and a review checklist.

Call Cheshire Terminal REST, MCP, discovery, and developer API surfaces for Solana agents, arena rooms, Upstash boxes, trading health, and OpenAPI. Use when integrating cheshireterminal.ai, /mcp, /.well-known/agent-card.json, ct_sk_ API keys, arena coordination, box handoff, or Apigee/zero-service health probes.

Automates GDPR Data Subject Access Request (DSAR) workflows including identity verification, PII discovery across databases and files using regex and NER, data mapping, response templating per Article 15 requirements, deadline tracking, and audit logging.

Breaks down a company's business model, revenue signals, positioning, pricing, moat, and weak points into a fixed, comparable template with fact-versus-inference labeling.

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Builds a Power × Interest stakeholder map and generates a communication plan per quadrant. Use when managing a complex launch, aligning cross-functional teams, or preparing stakeholder engagement strategy. Triggers on: stakeholder management, stakeholder map, stakeholder alignment, communication plan, power interest grid, cross-functional alignment, executive alignment, managing up.

Run Mom Test–style customer-discovery interviews to validate or kill an unbuilt idea — generate a non-leading interview guide, conduct or coach the conversations, and synthesize signal vs compliments. Load when the user asks to do customer discovery, run problem interviews, validate an idea with users, run a Mom Test, design an interview guide, or says "talk to customers", "validate the problem", "interview users", "Mom Test this", "did real users want it", "synthesize my interviews", "I just talked to N people". Sub-skill of `venture-exploration`. Hard-bans "would you use this?", solution-pitching, friend/family-only ICP, and treating compliments as validation. Calls `secure-*` before synthesizing any pasted external transcripts.

Migrates legacy AEM (6.x, AMS, on-prem) to AEM as a Cloud Service using BPA CSV or CAM/MCP target discovery, with one-pattern-per-session workflow for scheduler, replication, event listener, HTL lint, dialog, and custom widget migration.

Query the Open Targets Platform GraphQL API for target-disease associations, tractability and safety data, genetics/omics evidence, and known drugs. Use when identifying or prioritizing therapeutic drug targets, assessing target druggability/safety, or gathering target-disease evidence for drug discovery. Part of the AlterLab Academic Skills suite.

Generate comprehensive email marketing strategy with 90-day implementation roadmap. Analyzes business type (local-business, saas, ecommerce, creator, agency) to deliver industry-specific segmentation plans, automation sequences, content calendars, KPI targets, platform recommendations, and week-by-week rollout schedule. Use when building email program from scratch or restructuring existing strategy.

A funnel and account-scoring diagnostic engine for any sales org. Connect a CRM and a product-analytics tool (plus optional enrichment, community, and meeting tools). Three modes. (1) FUNNEL DIAGNOSIS finds leaky conversion gates by channel with per-stage leakage, dollarized leverage points, and cohort velocity. (2) SPRINT PLANNING enriches qualified accounts into a ranked backlog with verified buying committees. (3) SCORING AUDIT finds where your scoring model is missing real ICPs. Trigger on 'funnel diagnosis', 'diagnose the funnel', 'where are we leaking', 'why is [channel] underperforming', 'conversion by channel', 'sprint planning', 'score these accounts', 'find missed ICPs', 'audit the scoring model', or any channel-level cohort-conversion, account-prioritization, or scoring-gap question.

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc