Product & Planning

rodrigomardones Bundle

Install, analyze, bootstrap, run, review, or migrate a Handyman agent harness: leader/implementer/reviewer roles work one feature at a time with disk state and executable verification. Triggers: harness or subagent workflow, feature_list.json, AGENTS.md, CHECKPOINTS.md, progress/, backlog/, HARNESS_WORKSPACE, .handyman, $HOME/HANDYMAN, per-role models/tools, anti-telefono-descompuesto, Obsidian vault harness. DO NOT USE FOR generic coding without the harness workflow.

rivet-dev Skill

Convert a spec into a Ralph the Riveter PRD and run folder for `riveter run`. Triggered by "riveter create run", "create a prd for riveter", "spec out", "plan this feature for riveter", or "convert this spec for riveter". Non-interactive — does not ask follow-up questions.

rqzhu-aide Bundle

Explicit-use interactive causal consulting team. Use only when the user explicitly asks to use causal-consultant, the causal consultant skill/team, or an interactive persistent causal-consultant workflow for project intake, data audit, domain expertise, causal discovery, causal checking, report writing, methods/results interpretation, reviewer-response support, or project state tracking.

robcsaszar Bundle

Plans a body of work into a durable decision map — a plans/ file by default, or a configured issue tracker — and a route of tracer-bullet tickets. Use whenever the user wants to plan something out — a feature or bug that needs scoping before code, an idea too vague to act on, a wish to brainstorm directions, or a feeling of being stuck in obvious ideas — even if they don't ask for a formal plan. Also use to chart a new map or, once its frontier is empty, to write its spec and route. Trigger phrases — plan this out, help planning, let's brainstorm, scope this, break this down, turn this idea into a plan, roadmap this, chart the route, to spec, to tickets. Don't use for working or implementing a ticket on an existing map (transit), naming or wording brainstorms, personal or event logistics, tasks the user mainly wants done now, a quick sketch of a small in-session change, auditing existing code (crucible), interrogating shipped work (socratic), or reviewing how the session was conducted (retrospective).

roeibh Bundle

Generate a self-contained interactive HTML artifact from a spec, plan, or PRD so the developer can click through it, comment inline on any component or section, and submit those comments back to Claude — turning the HTML into a closed review loop, not a one-shot mockup. Use this skill whenever the user has just finished brainstorming a feature, has a spec or plan committed to `docs/superpowers/specs/` or `docs/superpowers/plans/`, mentions specs, plans, PRDs, design docs, requirements, mockups, or wireframes, says things like "make this concrete", "let me see it", "visualize the spec", "build a prototype of this", "turn this into a mockup", wants to review or iterate on a spec, or returns with a `feedback.json` or pasted feedback payload from a previously generated interactive spec. Especially use this right after `brainstorming` produces a design doc — offer it proactively then. Also triggers when the user says just "submitted", "feedback ready", "feedback sent", "applied", or similar short messages indicati

rusel95 Bundle

AI Copilot and free alternative to Astro MCP for this repo's App Store app: keyword rank tracking, live search hints, competitor audit, ASO / keyword iteration, App Store release readiness, Apple Ads setup and economics, product-page experiments, reviews, and content backlog. Reads a persistent state store from the current repo's own marketing/ directory and answers 'where am I, what's next' — never starts from zero.

ronaldtebrake Bundle

Review code according to Drupal's official coding standards. Provides AI agents with comprehensive guidelines for PHP, JavaScript, CSS, Twig, YAML, SQL, and markup files in Drupal projects. Uses dynamic context discovery to load only relevant standards based on file type being reviewed.

s1dd4rth Bundle

Facilitate business analysis work using IIBA's BABOK Guide v3 — six knowledge areas, thirty tasks, fifty techniques, five perspectives. Use whenever the user is doing BA work: scoping a change, eliciting requirements, modelling a process, mapping stakeholders, prioritizing a backlog, evaluating a solution, building a business case, choosing between solution options, or running a workshop. Trigger even when the user doesn't say "BABOK" — phrases like "starting a discovery", "help me gather requirements", "we need to evaluate this solution", "map stakeholders", "what techniques should I use", "how do I prioritize", or "right approach for this analysis" are all in scope. Also trigger for the BACCM lens (Change, Need, Solution, Stakeholder, Value, Context), technique-to-task lookup, and Agile/BI/IT/Business Architecture/BPM perspective requests. Acts as a coach, not a textbook — picks Quick/Working/Full depth and walks the user through tasks.

sakshi-gupta-1 Bundle

Runs a brutal, evidence-first teardown of a startup/app idea in one of two modes — solo-dev side-income screen (default: build effort, Play Store/ASO crowding, realistic solo income, ship-it-or-skip verdict) or VC-scale investment teardown (market sizing, moats, unit economics, funding verdict) — producing a full research report either way. Use whenever the user pastes a startup/product/app idea and asks to evaluate, roast, stress-test, or tear it apart, tell them if it's good, do a pre-mortem, or asks "should I build this" / "is this worth pursuing" / "is this a good side-income idea" — even without the word "teardown". Also trigger for one-line ideas dropped mid-conversation if the user is clearly asking for real evaluation, not brainstorming. Do NOT use for open-ended ideation or for a PRD on something already committed — use a general brainstorming or spec-writing tool instead. Assumes the idea is bad until evidence says otherwise — never use if the user wants encouragement or a first-draft pitch.

sambernhardt Skill

Install and work with uifork, a CLI tool and React component library for managing UI component versions. Use when the user wants to version components, test UI variations, gather stakeholder feedback, or work with uifork commands like init, watch, new, fork, promote.

sametcn99 Bundle

Use when creating, refining, or validating product planning documents (project brief, PRD, roadmap, architecture notes, task breakdown, risks).