Product & Planning

knuckles-team Bundle

Run hypothesis-driven, scoped research, graph mining, learning, causal analysis, and evaluation in Graph-OS. Use for reproducible multi-source studies, comparative analysis, anomaly or association discovery, graph learning, causal evaluation, feedback, report persistence, or grounded proposals. For one bounded lookup or cited explanation, use graph-query-and-explanation.

knuckles-team Bundle

Configure, observe, audit, secure, and troubleshoot an already-installed Graph-OS runtime. Use for health checks, incidents, compliance, sessions, traces, cache or secret operations, tool discovery and loading, intent routing, policy verification, coverage checks, or recovery within the deployed topology. For provisioning, profile changes, topology changes, connector rollout, or upgrades, use agent-utilities-deployment.

bhangeef16 Skill

Use whenever a delivery run needs a Knowledge Object created from its template or an existing one updated to reflect changed behavior: filing a business rule, requirement, ADR, user story, or any other graph-node fact into the knowledge graph, or writing/updating a non-graph prose document (an ExecPlan, a query/roadmap/test-strategy document) under the run workspace. This is the promote_to_product_knowledge action of the planning stretch, the documentation_update action of the implementation stretch, and the ADR-drafting half of technical_design's stop condition — one Agent-tool dispatch each, parameterized by doctype and mode, distinct from the later review-evidence documentation_evidence_review pass that judges this work, not produces it.

bhangeef16 Skill

Use when a delivery run needs PRD-style requirements produced from a user request: extracting every atomic requirement, rule, decision, and story into a classified requirement register, naming actors and protected actions, recording assumptions, open questions, and acceptance criteria. This is the gather_requirements action of the planning stretch — one Agent-tool dispatch with subagent_type business-analyst — distinct from resolve-open-questions (which answers the questions this action raises) and promote-to-product-knowledge (which files the resolved rows).

aojdevstudio Bundle

Linear issue management via linearis CLI with team inference. USE WHEN linear, issues, tasks, tickets, backlog, sprint, resolve issue, ship issue, plan project, break down feature, ship daily, what should I work on.

mickzijdel Skill

Use when a plan, design, or feature idea needs to be interrogated until it is fully specified — the user wants to be interviewed, one question at a time, until every open decision is resolved. Triggers on "grill me", "interview me", "ask me questions about this", "stress-test this plan with me", "help me fully specify this", or before writing a plan/PRD from a still-fuzzy idea — offer to grill first rather than drafting from guesses. Not for generating ideas from scratch (that's brainstorming), third-party critique (that's [[board]]), or failure-mode hunting (that's [[premortem]]).

mickzijdel Skill

Use when working through a repo's `plans/off-topic-improvements.md` backlog — the out-of-scope improvements noted during earlier work. Triggers on "drain the backlog", "address the off-topic improvements", "tackle the off-topic backlog", "work through the improvements file", or clearing accumulated backlog items. Triages each item (do now / defer / drop), lands each addressed item as its own atomic commit, and keeps the backlog file in sync. NOT for finding new improvements (that's a review) or a single ad-hoc fix.

cerico Skill

Pull unassigned or backlog Linear issues, grade by urgency, and suggest what to work on next.

kenlck Bundle

Research and maintain an evidence-backed SEO/GEO thesis, opportunity portfolio, and execution-ready roadmap.

kenlck Skill

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

kenlck Bundle

Create a PRD with an embedded Design Direction section through user interview, codebase exploration, and design intent capture. Use when building or revamping any feature with frontend or UI work — landing pages, components, UI redesigns — where design intent needs to be locked in before implementation. Extends the standard PRD process with structured design thinking: audience, tone, aesthetic direction, and the one memorable differentiator.

yesterday-ai Skill

Autonomous project execution engine for AI agents. Orchestrates scheduled cron jobs per project using workflow templates (dev-autonomous, research, ops). Integrates PR-Gate, GitHub workflow, ROADMAP tracking, and human notification via project-tracking. Use when: setting up scheduled project work, running an autonomous session, or designing an agent's development loop. Builds on forward-momentum (philosophy) and implements it as a concrete system.

sylphxai Skill

Feature discovery - competitive analysis. Use when exploring features.

jnemargut Skill

General-purpose planning skill that creates a research-backed operational roadmap for any complex goal. Career transitions, legal battles, major life changes, organizational challenges, or anything where you need a concrete phased plan with specific tasks. Each task tagged as requiring you personally, AI assistance, or fully automatable.

jnemargut Bundle

Experimental v2 of /game-plan. Same soul — a research-backed phased operational roadmap for any complex goal, every task tagged human/AI-assisted/automatable — plus: parallel research including failure stories, a day-by-day Week One, dependency tags on tasks, per-phase checkpoint gates with pivot criteria, and automatic conversion of your strategy brief's tripwires into recurring check-in tasks. Reads /whoiam and /research-sources config.

jnemargut Bundle

Product planning skill that generates a research-backed launch roadmap — operations, partnerships, trust-building, product evolution, and go-to-market execution. Each task tagged as human-only, AI-assisted, or automatable. Part of the Product Pipeline: use after /product-strategy and before /product-design.

jnemargut Bundle

Generate a unique AI-driven design system through a guided designer workshop. Walks the user through archetype selection, adjective sliders, reference triage, and signature tension — then generates novel SVG icons, a curated Google Fonts pairing, a semantic palette, and an applied showcase HTML + framework-agnostic bundle that any generator (Claude Code, v0, Lovable) can adopt. Every generated choice must trace to a workshop signal (amplification rules), nothing on the banned-defaults list ships, and the showcase passes a render-and-critique gate. Produces 'design/' folder with showcase.html, tokens.json, tokens.css, icons/, and claude.md. Use when the user wants a unique design system (colors, components, typography, icons) generated through discovery — not another shadcn-looking default. Triggers on 'design system', 'brand identity', 'make it unique', 'curated typography', 'not generic', 'design DNA'.

zhuochun Bundle

Build a disposable, runnable software prototype that answers one explicit behavior, state, UI, or interaction design question before maintained implementation. Use when users want to compare runnable candidates, exercise an interaction direction before choosing maintained behavior, or drive candidate rules or state models through cases. Route customer-value experiments to product-opportunity-discovery and production changes to scoped-change-implementation.

zhuochun Bundle

Orient across multiple architecture surfaces of unfamiliar software or trace one bounded end-to-end journey across experience, operations, domain state, systems, data, interfaces, and owners. Use when a decision depends on cross-surface relationships or expected and observed paths disagree. Keep simple lookups direct; route architecture judgment, product discovery, and redesign elsewhere.

zhuochun Bundle

Discover and test which customer opportunity and solution direction merits investment before heavy implementation. Use for solution-shaped feature requests, conflicting customer evidence, opportunity models, assumption mapping, prototypes, experiments, or comparisons among solutions. Produce an evidence-based learn, narrow, pivot, stop, or proceed recommendation; exclude roadmap allocation and implementation of accepted work.

zhuochun Bundle

Design a reviewable user experience for an intended outcome through user-facing concepts, task flows, information hierarchy, interaction states, feedback, and recovery. Use before implementation when people would otherwise invent consequential UX choices. Route opportunity validation to product discovery, fixed-candidate review to specification-review, and small clear edits directly to implementation.

zhuochun Bundle

Reconsider one completed software design after implementation, repeated change, operation, incidents, support, or ownership creates a material knowledge delta. Recover commitments, compare alternatives, and recommend retain, quarantine, prune, reshape, or rebuild without modification. Exclude portfolio discovery, routine implementation review, weak first design passes, and already-decided refactors; use architecture-assessment for broad investment ranking.

zhuochun Bundle

Prioritize product opportunities and bets against explicit outcomes, strategy, customer evidence, obligations, capacity, dependencies, risk, and learning horizon. Use for outcome roadmaps, reframing feature backlogs, choosing among customer problems, balancing near-term and uncertain bets, or reviewing allocation. Exclude company-wide capital governance, discovery from scratch, and delivery sequencing after priorities are accepted.

mshadmanrahman Skill

Write product requirements documents at variable depth: one-pager, brief, full PRD, or RFC. Auto-detects depth from context. Reads existing research and context if available. Triggers on: "write a PRD", "product spec", "one-pager", "RFC", "requirements doc", "spec for", "brief for".

mshadmanrahman Bundle

Pull all open bugs from Jira, Linear, or GitHub Issues into a local backlog file. Read-only. Use before a triage run, or when the local backlog is stale.

mshadmanrahman Skill

Open a focused investigation session for one bug: pull its full tracker detail, load past lessons and triage history, and produce an investigation plan. Use when starting work on a single ticket, after /shepherd-sync has built the backlog.

mshadmanrahman Bundle

Launch parallel agents to check whether old bugs still reproduce on the live site, turning a stale backlog into a prioritized verified list. Use when a bug backlog needs cleaning without reading code.

mshadmanrahman Bundle

Runs a full product discovery cycle for PMs with no UX researcher: frames the problem, plans Mom Test interviews, synthesizes findings into an opportunity tree, and packages evidence into a stakeholder one-pager. Use when the user wants to start discovery, validate a problem before building, plan customer interviews, turn interview notes into themes, or present research evidence to stakeholders. Triggers on "start product discovery", "validate this problem", "plan customer interviews", "synthesize my research", "package this for stakeholders".

mshadmanrahman Skill

Transform a single customer interview transcript into a structured Interview Snapshot with five fixed sections. Use when the user has a Granola/Fireflies/manual transcript and needs the atomic research unit that feeds cross-interview synthesis. Triggers on "create interview snapshot", "process this interview", "synthesize this one interview", "turn this transcript into a snapshot". Prerequisite for any cross-interview synthesis step in discovery-process.

ahmet-talha-kavakli Skill

Essential tools and frameworks for modern product management, from discovery to delivery.

bbengamin Bundle

Split a shared growth strategy or inbound branch artifact into one level of Paperclip backlog work items for inbound, content-led, or channel-led acquisition. Use when planning LinkedIn, newsletter, YouTube, personal-brand, or content work after growth-record-strategy.

bbengamin Bundle

Split a shared growth strategy or outbound branch artifact into one level of Paperclip backlog work items for outbound acquisition. Use when planning lead sourcing, enrichment, personalization, sequences, reply handling, operator walkthrough booking, warm intros, or outbound validation work after growth-record-strategy.

bbengamin Bundle

Decompose a Paperclip strategy artifact or parent issue into one level of backlog child issues. Use when turning a Paperclip plan into planned issue structure or planning parent issues, before triage or delegation.

bhagyamudgal Bundle

Discovery interview before writing code on a new project. Interrogate requirements, stack, and conventions, then emit CLAUDE.md, PATTERNS.md and the project's lib/ scaffolding. Use when the user starts a new project, or when they seem unsure about a technical decision that will be expensive to reverse.

huruikagi Bundle

Turn a change request or Source Collection into confirmed Spec and milestone boundaries.

huruikagi Bundle

Implement or resume one roadmap item — executing a Spec's approved task plan through returned review or diagnosis with dispatched implementers and reviewers, or performing and completing a Direct change. Do not use for a diagnosis-only request asking why work failed or cannot be implemented.