Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and rationale come for free. Refuses a brief that is not ready; shows the whole tree and waits before writing. Use for "build the backlog", "turn the brief into issues".

Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with ranked charts, a three-month trend, a multi-year overlay and a data table. Use when asked to benchmark a product against competitors, size up a market, answer "how much traffic does X get compared to Y", build a competitive landscape, or produce a traffic/authority comparison deck or page.

Guide a product discovery conversation and write product-brief.md with the problem, evidence, scope, decisions, and the next uncertainty to resolve. Use for product discovery, defining a product, or refreshing its brief. Supports existing products, client ideas, and own ideas.

Turn vague intent into a precise, executable spec in five phases. (gstack)

Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop

Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

Includes Ce Babysit Pr, Ce Bakeoff, Ce Brainstorm, Ce Code Review, Ce Commit, Ce Commit Push Pr, Ce Compound, Ce Compound Refresh, Ce Debug, Ce Doc Review, Ce Dogfood, Ce Explain, Ce Handoff, Ce Ideate, Ce Noslop, Ce Optimize, Ce Plan, Ce Polish, Ce Pov, Ce Product Pulse, Ce Promote, Ce Proof, Ce Prototype, Ce Resolve Pr Feedback, Ce Retune, Ce Riffrec Feedback Analysis, Ce Setup, Ce Simplify Code, Ce Strategy, Ce Sweep, Ce Test Browser, Ce Test Xcode, Ce Work, Ce Worktree, Lfg, Wtf

Sweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lfg`-ready plan. First run sets up sources; supports mode:non-interactive for scheduled runs.

Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.

Generate time-windowed product pulse reports from configured signals.

Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.

Includes Ab Test Analysis, Analyze Feature Requests, Ansoff Matrix, Beachhead Segment, Brainstorm Experiments Existing, Brainstorm Experiments New, Brainstorm Ideas Existing, Brainstorm Ideas New, Brainstorm Okrs, Business Model, Code Review, Cohort Analysis, Competitive Battlecard, Competitor Analysis, Create Prd, Customer Journey Map, Draft Nda, Dummy Dataset, Grammar Check, Growth Loops, Gtm Motions, Gtm Strategy, Ideal Customer Profile, Identify Assumptions Existing, Identify Assumptions New, Intended Vs Implemented, Interview Script, Job Stories, Lean Canvas, Market Segments, Market Sizing, Marketing Ideas, Metrics Dashboard, Monetization Strategy, North Star Metric, Opportunity Solution Tree, Outcome Roadmap, Pestle Analysis, Porters Five Forces, Positioning Ideas, Pre Mortem, Pricing Strategy, Prioritization Frameworks, Prioritize Assumptions, Prioritize Features, Privacy Policy, Product Name, Product Strategy, Product Vision, Release Notes, Retro, Review Resume, Sentiment Analysis, Shipping Artifacts, Sprint Plan, Sql Queries, Stakeholder Map, Startup Canvas, Strategy Red Team, Summarize Interview, Summarize Meeting, Swot Analysis, Test Scenarios, User Personas, User Segmentation, User Stories, Value Prop Statements, Value Proposition, Wwas

Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill. Runs before om-spec-writing and om-prepare-issue. Use when the user says "should we build this", "let's think this through", "I have an idea", "is this worth doing".

Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, checks each issue against SDLC.md's Definition of Ready (READY_STATUS, not-ready comment), and flags feature issues lacking a covering spec (optionally authoring one with --write-missing-specs). Single issue or a batch (last ~25 open, worst-described first). Idempotent, claim-aware.

Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.

Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust private VPC networking, or Private Service Connect. Don't use for VM, GKE, or non-Google Cloud architectures.

Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated best practices and architecture guidance. Use when users need agentic assistance to design and create a multi-product solution in the cloud for live bidirectional multimodal streaming workloads. Don't use for simple text-based chat applications or workloads without real-time streaming requirements.

Discovers requirements and designs a borderless open data lakehouse using Lakehouse for Apache Iceberg and BigQuery data agents. Use when architecting multi-cloud storage infrastructure (Cloud Storage, AWS S3, Azure Blob), establishing ingestion and AI serving subsystems, configuring Cross-Cloud Interconnect, or deploying Gemini Enterprise Agent Platform and BigQuery data agents. Don't use for single-cloud data warehouses, or when the focus is on Knowledge Catalog metadata governance and Spark-driven IDE analytics workflows (use google-cloud-solution-agentic-analytics-spark-knowledge-catalog instead).

Cinematic 5–10s product ad from a product photo + brand brief.

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and rationale come for free. Refuses a brief that is not ready; shows the whole tree and waits before writing. Use for "build the backlog", "turn the brief into issues".

Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with ranked charts, a three-month trend, a multi-year overlay and a data table. Use when asked to benchmark a product against competitors, size up a market, answer "how much traffic does X get compared to Y", build a competitive landscape, or produce a traffic/authority comparison deck or page.

Guide a product discovery conversation and write product-brief.md with the problem, evidence, scope, decisions, and the next uncertainty to resolve. Use for product discovery, defining a product, or refreshing its brief. Supports existing products, client ideas, and own ideas.

Turn vague intent into a precise, executable spec in five phases. (gstack)

Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop

Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

Includes Ce Babysit Pr, Ce Bakeoff, Ce Brainstorm, Ce Code Review, Ce Commit, Ce Commit Push Pr, Ce Compound, Ce Compound Refresh, Ce Debug, Ce Doc Review, Ce Dogfood, Ce Explain, Ce Handoff, Ce Ideate, Ce Noslop, Ce Optimize, Ce Plan, Ce Polish, Ce Pov, Ce Product Pulse, Ce Promote, Ce Proof, Ce Prototype, Ce Resolve Pr Feedback, Ce Retune, Ce Riffrec Feedback Analysis, Ce Setup, Ce Simplify Code, Ce Strategy, Ce Sweep, Ce Test Browser, Ce Test Xcode, Ce Work, Ce Worktree, Lfg, Wtf

Sweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lfg`-ready plan. First run sets up sources; supports mode:non-interactive for scheduled runs.

Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.

Generate time-windowed product pulse reports from configured signals.

Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.

Includes Ab Test Analysis, Analyze Feature Requests, Ansoff Matrix, Beachhead Segment, Brainstorm Experiments Existing, Brainstorm Experiments New, Brainstorm Ideas Existing, Brainstorm Ideas New, Brainstorm Okrs, Business Model, Code Review, Cohort Analysis, Competitive Battlecard, Competitor Analysis, Create Prd, Customer Journey Map, Draft Nda, Dummy Dataset, Grammar Check, Growth Loops, Gtm Motions, Gtm Strategy, Ideal Customer Profile, Identify Assumptions Existing, Identify Assumptions New, Intended Vs Implemented, Interview Script, Job Stories, Lean Canvas, Market Segments, Market Sizing, Marketing Ideas, Metrics Dashboard, Monetization Strategy, North Star Metric, Opportunity Solution Tree, Outcome Roadmap, Pestle Analysis, Porters Five Forces, Positioning Ideas, Pre Mortem, Pricing Strategy, Prioritization Frameworks, Prioritize Assumptions, Prioritize Features, Privacy Policy, Product Name, Product Strategy, Product Vision, Release Notes, Retro, Review Resume, Sentiment Analysis, Shipping Artifacts, Sprint Plan, Sql Queries, Stakeholder Map, Startup Canvas, Strategy Red Team, Summarize Interview, Summarize Meeting, Swot Analysis, Test Scenarios, User Personas, User Segmentation, User Stories, Value Prop Statements, Value Proposition, Wwas

Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill. Runs before om-spec-writing and om-prepare-issue. Use when the user says "should we build this", "let's think this through", "I have an idea", "is this worth doing".

Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, checks each issue against SDLC.md's Definition of Ready (READY_STATUS, not-ready comment), and flags feature issues lacking a covering spec (optionally authoring one with --write-missing-specs). Single issue or a batch (last ~25 open, worst-described first). Idempotent, claim-aware.

Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.

Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust private VPC networking, or Private Service Connect. Don't use for VM, GKE, or non-Google Cloud architectures.

Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated best practices and architecture guidance. Use when users need agentic assistance to design and create a multi-product solution in the cloud for live bidirectional multimodal streaming workloads. Don't use for simple text-based chat applications or workloads without real-time streaming requirements.

Discovers requirements and designs a borderless open data lakehouse using Lakehouse for Apache Iceberg and BigQuery data agents. Use when architecting multi-cloud storage infrastructure (Cloud Storage, AWS S3, Azure Blob), establishing ingestion and AI serving subsystems, configuring Cross-Cloud Interconnect, or deploying Gemini Enterprise Agent Platform and BigQuery data agents. Don't use for single-cloud data warehouses, or when the focus is on Knowledge Catalog metadata governance and Spark-driven IDE analytics workflows (use google-cloud-solution-agentic-analytics-spark-knowledge-catalog instead).

Cinematic 5–10s product ad from a product photo + brand brief.

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and rationale come for free. Refuses a brief that is not ready; shows the whole tree and waits before writing. Use for "build the backlog", "turn the brief into issues".

Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with ranked charts, a three-month trend, a multi-year overlay and a data table. Use when asked to benchmark a product against competitors, size up a market, answer "how much traffic does X get compared to Y", build a competitive landscape, or produce a traffic/authority comparison deck or page.

Guide a product discovery conversation and write product-brief.md with the problem, evidence, scope, decisions, and the next uncertainty to resolve. Use for product discovery, defining a product, or refreshing its brief. Supports existing products, client ideas, and own ideas.

Turn vague intent into a precise, executable spec in five phases. (gstack)

Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop

Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

Includes Ce Babysit Pr, Ce Bakeoff, Ce Brainstorm, Ce Code Review, Ce Commit, Ce Commit Push Pr, Ce Compound, Ce Compound Refresh, Ce Debug, Ce Doc Review, Ce Dogfood, Ce Explain, Ce Handoff, Ce Ideate, Ce Noslop, Ce Optimize, Ce Plan, Ce Polish, Ce Pov, Ce Product Pulse, Ce Promote, Ce Proof, Ce Prototype, Ce Resolve Pr Feedback, Ce Retune, Ce Riffrec Feedback Analysis, Ce Setup, Ce Simplify Code, Ce Strategy, Ce Sweep, Ce Test Browser, Ce Test Xcode, Ce Work, Ce Worktree, Lfg, Wtf

Sweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lfg`-ready plan. First run sets up sources; supports mode:non-interactive for scheduled runs.

Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.

Generate time-windowed product pulse reports from configured signals.

Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.

Includes Ab Test Analysis, Analyze Feature Requests, Ansoff Matrix, Beachhead Segment, Brainstorm Experiments Existing, Brainstorm Experiments New, Brainstorm Ideas Existing, Brainstorm Ideas New, Brainstorm Okrs, Business Model, Code Review, Cohort Analysis, Competitive Battlecard, Competitor Analysis, Create Prd, Customer Journey Map, Draft Nda, Dummy Dataset, Grammar Check, Growth Loops, Gtm Motions, Gtm Strategy, Ideal Customer Profile, Identify Assumptions Existing, Identify Assumptions New, Intended Vs Implemented, Interview Script, Job Stories, Lean Canvas, Market Segments, Market Sizing, Marketing Ideas, Metrics Dashboard, Monetization Strategy, North Star Metric, Opportunity Solution Tree, Outcome Roadmap, Pestle Analysis, Porters Five Forces, Positioning Ideas, Pre Mortem, Pricing Strategy, Prioritization Frameworks, Prioritize Assumptions, Prioritize Features, Privacy Policy, Product Name, Product Strategy, Product Vision, Release Notes, Retro, Review Resume, Sentiment Analysis, Shipping Artifacts, Sprint Plan, Sql Queries, Stakeholder Map, Startup Canvas, Strategy Red Team, Summarize Interview, Summarize Meeting, Swot Analysis, Test Scenarios, User Personas, User Segmentation, User Stories, Value Prop Statements, Value Proposition, Wwas

Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill. Runs before om-spec-writing and om-prepare-issue. Use when the user says "should we build this", "let's think this through", "I have an idea", "is this worth doing".

Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, checks each issue against SDLC.md's Definition of Ready (READY_STATUS, not-ready comment), and flags feature issues lacking a covering spec (optionally authoring one with --write-missing-specs). Single issue or a batch (last ~25 open, worst-described first). Idempotent, claim-aware.

Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.

Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust private VPC networking, or Private Service Connect. Don't use for VM, GKE, or non-Google Cloud architectures.

Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated best practices and architecture guidance. Use when users need agentic assistance to design and create a multi-product solution in the cloud for live bidirectional multimodal streaming workloads. Don't use for simple text-based chat applications or workloads without real-time streaming requirements.

Discovers requirements and designs a borderless open data lakehouse using Lakehouse for Apache Iceberg and BigQuery data agents. Use when architecting multi-cloud storage infrastructure (Cloud Storage, AWS S3, Azure Blob), establishing ingestion and AI serving subsystems, configuring Cross-Cloud Interconnect, or deploying Gemini Enterprise Agent Platform and BigQuery data agents. Don't use for single-cloud data warehouses, or when the focus is on Knowledge Catalog metadata governance and Spark-driven IDE analytics workflows (use google-cloud-solution-agentic-analytics-spark-knowledge-catalog instead).

Cinematic 5–10s product ad from a product photo + brand brief.

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and rationale come for free. Refuses a brief that is not ready; shows the whole tree and waits before writing. Use for "build the backlog", "turn the brief into issues".

Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with ranked charts, a three-month trend, a multi-year overlay and a data table. Use when asked to benchmark a product against competitors, size up a market, answer "how much traffic does X get compared to Y", build a competitive landscape, or produce a traffic/authority comparison deck or page.

Guide a product discovery conversation and write product-brief.md with the problem, evidence, scope, decisions, and the next uncertainty to resolve. Use for product discovery, defining a product, or refreshing its brief. Supports existing products, client ideas, and own ideas.

Turn vague intent into a precise, executable spec in five phases. (gstack)

Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop

Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

Includes Ce Babysit Pr, Ce Bakeoff, Ce Brainstorm, Ce Code Review, Ce Commit, Ce Commit Push Pr, Ce Compound, Ce Compound Refresh, Ce Debug, Ce Doc Review, Ce Dogfood, Ce Explain, Ce Handoff, Ce Ideate, Ce Noslop, Ce Optimize, Ce Plan, Ce Polish, Ce Pov, Ce Product Pulse, Ce Promote, Ce Proof, Ce Prototype, Ce Resolve Pr Feedback, Ce Retune, Ce Riffrec Feedback Analysis, Ce Setup, Ce Simplify Code, Ce Strategy, Ce Sweep, Ce Test Browser, Ce Test Xcode, Ce Work, Ce Worktree, Lfg, Wtf

Sweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lfg`-ready plan. First run sets up sources; supports mode:non-interactive for scheduled runs.

Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.

Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).

Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.

Generate time-windowed product pulse reports from configured signals.

Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.

Includes Ab Test Analysis, Analyze Feature Requests, Ansoff Matrix, Beachhead Segment, Brainstorm Experiments Existing, Brainstorm Experiments New, Brainstorm Ideas Existing, Brainstorm Ideas New, Brainstorm Okrs, Business Model, Code Review, Cohort Analysis, Competitive Battlecard, Competitor Analysis, Create Prd, Customer Journey Map, Draft Nda, Dummy Dataset, Grammar Check, Growth Loops, Gtm Motions, Gtm Strategy, Ideal Customer Profile, Identify Assumptions Existing, Identify Assumptions New, Intended Vs Implemented, Interview Script, Job Stories, Lean Canvas, Market Segments, Market Sizing, Marketing Ideas, Metrics Dashboard, Monetization Strategy, North Star Metric, Opportunity Solution Tree, Outcome Roadmap, Pestle Analysis, Porters Five Forces, Positioning Ideas, Pre Mortem, Pricing Strategy, Prioritization Frameworks, Prioritize Assumptions, Prioritize Features, Privacy Policy, Product Name, Product Strategy, Product Vision, Release Notes, Retro, Review Resume, Sentiment Analysis, Shipping Artifacts, Sprint Plan, Sql Queries, Stakeholder Map, Startup Canvas, Strategy Red Team, Summarize Interview, Summarize Meeting, Swot Analysis, Test Scenarios, User Personas, User Segmentation, User Stories, Value Prop Statements, Value Proposition, Wwas

Divergent conversation before any artifact exists — open questions one at a time, alternatives including building nothing, converging on a routing decision and a handoff brief for the next skill. Runs before om-spec-writing and om-prepare-issue. Use when the user says "should we build this", "let's think this through", "I have an idea", "is this worth doing".

Bring existing tracker issues up to standard without implementing anything — applies missing SDLC labels, clarifies laconic issues (analyzing attached screenshots), posts a read-only implementation-prep analysis, checks each issue against SDLC.md's Definition of Ready (READY_STATUS, not-ready comment), and flags feature issues lacking a covering spec (optionally authoring one with --write-missing-specs). Single issue or a batch (last ~25 open, worst-described first). Idempotent, claim-aware.

Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.

Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust private VPC networking, or Private Service Connect. Don't use for VM, GKE, or non-Google Cloud architectures.

Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated best practices and architecture guidance. Use when users need agentic assistance to design and create a multi-product solution in the cloud for live bidirectional multimodal streaming workloads. Don't use for simple text-based chat applications or workloads without real-time streaming requirements.

Discovers requirements and designs a borderless open data lakehouse using Lakehouse for Apache Iceberg and BigQuery data agents. Use when architecting multi-cloud storage infrastructure (Cloud Storage, AWS S3, Azure Blob), establishing ingestion and AI serving subsystems, configuring Cross-Cloud Interconnect, or deploying Gemini Enterprise Agent Platform and BigQuery data agents. Don't use for single-cloud data warehouses, or when the focus is on Knowledge Catalog metadata governance and Spark-driven IDE analytics workflows (use google-cloud-solution-agentic-analytics-spark-knowledge-catalog instead).

Cinematic 5–10s product ad from a product photo + brand brief.