[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7357B48F8MK86EQF135FJQ6":3,"skill-same:01M7357B48F8MK86EQF135FJQ6":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7357B48F8MK86EQF135FJQ6","productize-wwas",null,"Why-What-Acceptance. Use when writing backlog items in Why-What-Acceptance format, breaking features into independent valuable work, or adding strategic context to delivery items.","itseffi\u002Fproductize","itseffi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15998472?v=4","01M734C5RJ7CKRTPB3FX84VZV7","Effi","01M734C5S6B7FW62ZNWYBZ9GG7",3,"MIT","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-wwas\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: productize-wwas\ndescription: >-\n  Why-What-Acceptance. Use when writing backlog items in Why-What-Acceptance format, breaking\n  features into independent valuable work, or adding strategic context to delivery items.\n---\n\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Why-What-Acceptance\n\n## Productize Preamble\n\nBefore producing the artifact, implementation step, or code change, classify the work:\n\n- **User\u002Fpersona**: founder, product leader, AI PM, AI builder, stakeholder, or mixed\u002Funknown.\n- **Product stage**: idea, validation, PMF search, growth, scale, pivot, or unknown.\n- **Artifact mode**: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.\n- **Artifact format**: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.\n- **Evidence standard**: what is known, assumed, missing, and risky.\n- **Decision mode**: recommend, ask for a blocking input, or proceed with explicit assumptions.\n\nOperating rules:\n\n1. Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.\n2. Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.\n3. Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.\n4. Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.\n5. If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.\n6. Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.\n7. End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.\n8. Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.\n9. If you must ask a blocking question, use this compact format: `AskUserQuestion: \u003Cone question> Why it matters: \u003Cdecision it changes>`.\n10. Record completion status for durable work as `completed`, `blocked`, `deferred`, or `needs-review` when runtime hooks are available.\n\nArtifact format policy:\n\n- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.\n- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams\u002Ftables\u002Fcomparisons\u002Fscreenshots, the artifact is meant to be shared, or interaction\u002Fexport controls would help the user stay in the loop.\n- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.\n- HTML artifacts must be local-first and portable: one file, embedded CSS\u002FJS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.\n- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy\u002Fexport buttons when they improve review speed. Avoid decorative complexity that hides the decision.\n- For implementation work with ambiguities, use `$implementation-notes` when the user asks for a running notes file, especially `implementation-notes.html` or `implementation-notes.md`.\n\nRuntime hooks, if available:\n\n- Use `productize-workflow start \"\u003Cuser request>\"` at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.\n- Use `productize-workflow complete --id \u003Cid> --status completed|blocked|deferred|needs-review --artifact-type \u003Ctype> --summary \u003Csummary>` before ending durable product work; it records the artifact, saves context, and logs completion status.\n- Use `productize-update-check --strict` at the start of maintenance, setup, release, or generated-output work.\n- Use `productize-config` to read or write user\u002Fteam preferences such as persona, artifact mode, evidence threshold, or update-check policy.\n- Use `productize-session-log` to record important workflow decisions.\n- Use `productize-artifact-log` when a durable artifact is produced.\n- Use `productize-context-restore` before restarting long-running product work from scratch.\n- Use `productize-context-save` after producing a durable strategy, research, spec, or stakeholder artifact.\n- Use `productize-registry-search` or `productize-skill-router` when routing is ambiguous.\n- Use `productize-completion-status` to log whether the workflow completed, blocked, deferred, or needs review.\n\nTelemetry standard:\n\n- Keep telemetry local by default in `.productize\u002F` or `PRODUCTIZE_STATE_DIR`.\n- Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.\n\nCurrent skill metadata:\n\n- **Skill**: `wwas`\n- **Lifecycle**: Plan\n- **Category**: Delivery\n- **Primary artifact**: Why-What-Acceptance backlog items with strategic context and acceptance criteria\n\nUse when writing backlog items in Why-What-Acceptance format, breaking features into independent valuable work, or adding strategic context to delivery items.\n\n## Productize Contract\n\n- **Primary lifecycle**: Plan\n- **Supporting lifecycle**: Build With AI\n- **Primary artifact**: Why-What-Acceptance backlog items with strategic context and acceptance criteria\n- **Source method**: pm-skills-main\u002Fpm-execution\u002Fskills\u002Fwwas\u002FSKILL.md\n\n## Method\n\nCreate product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.\n\n**Use when:** Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.\n\n**Arguments:**\n- `$PRODUCT`: The product or system name\n- `$FEATURE`: The new feature or capability\n- `$DESIGN`: Link to design files (Figma, Miro, etc.)\n- `$ASSUMPTIONS`: Key assumptions and strategic context\n\n## Step-by-Step Process\n\n1. **Define the strategic Why** - Connect work to business and team objectives\n2. **Describe the What** - Keep descriptions concise, reference designs\n3. **Write Acceptance Criteria** - High-level, not detailed specifications\n4. **Ensure independence** - Items can be developed in any order\n5. **Keep items negotiable** - Invite team conversation, not constraints\n6. **Make items valuable** - Each delivers measurable user or business value\n7. **Ensure testability** - Outcomes are observable and verifiable\n8. **Size appropriately** - Small enough for one sprint estimate\n\n## Item Template\n\n**Title:** [What will be delivered]\n\n**Why:** [1-2 sentences connecting to strategic context and team objectives]\n\n**What:** [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]\n\n**Acceptance Criteria:**\n- [Observable outcome 1]\n- [Observable outcome 2]\n- [Observable outcome 3]\n- [Observable outcome 4]\n\n## Example WWA Item\n\n**Title:** Implement Real-Time Spending Tracker\n\n**Why:** Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.\n\n**What:** Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.\n\n**Acceptance Criteria:**\n- Spending totals update within 2 seconds of logging an expense\n- Budget progress is visually indicated with a progress bar\n- Users can see remaining budget amount at a glance\n- System handles multiple expense categories correctly\n\n## Output Deliverables\n\n- Complete set of backlog items for the feature\n- Each item includes Why, What, and Acceptance Criteria sections\n- Items are independent and deliverable in any order\n- Items are sized for estimation and completion in one sprint\n- Strategic context is clear for team decision-making\n- Design references are included for implementation guidance\n\n---\n\n### Further Reading\n\n- [How to Write User Stories: The Ultimate Guide](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-write-user-stories)\n\n## Productize Output Rules\n\n- Produce the artifact named in the Productize contract, not a generic framework summary.\n- Separate known facts, assumptions, missing evidence, and risky leaps before recommending.\n- Convert uncertain claims into validation steps, metrics, owner decisions, or launch\u002Freadout checks.\n- If this reference method conflicts with Productize evidence standards, keep the Productize standard.\n","\u003C!-- AUTO-GENERATED from SKILL.md.tmpl - do not edit directly -->\n\u003C!-- Regenerate: npm run skills:generate -->\n\n# Why-What-Acceptance\n\n## Productize Preamble\n\nBefore producing the artifact, implementation step, or code change, classify the work:\n\n- **User\u002Fpersona**: founder, product leader, AI PM, AI builder, stakeholder, or mixed\u002Funknown.\n- **Product stage**: idea, validation, PMF search, growth, scale, pivot, or unknown.\n- **Artifact mode**: strategy memo, PRD, research plan, positioning, experiment, deck, roadmap, execution brief, diagnostic, or decision record.\n- **Artifact format**: Markdown for short, repo-native, diff-sensitive artifacts; self-contained HTML for long, visual, shareable, interactive, or explicitly requested artifacts.\n- **Evidence standard**: what is known, assumed, missing, and risky.\n- **Decision mode**: recommend, ask for a blocking input, or proceed with explicit assumptions.\n\nOperating rules:\n\n1. Do not produce generic product strategy filler. Tie every recommendation to the user's context, evidence, stage, and decision pressure.\n2. Separate facts from assumptions. Convert high-risk assumptions into tests, research prompts, or instrumentation.\n3. Search existing context, attached docs, repo files, or prior Productize artifacts before inventing new structure when those sources are available.\n4. Ask only for inputs that materially change the output. If the next step is obvious, proceed and state assumptions.\n5. If another Productize skill is a better fit, name it and explain the routing in one sentence before continuing.\n6. Enforce the output contract for this skill. Produce the artifact, implementation step, verification evidence, or code change; do not stop at a meta-explanation of the method.\n7. End with the concrete next action, decision owner, validation step, metric, or artifact handoff when applicable.\n8. Use the user's saved Productize preferences when available, but do not let stale preferences override explicit instructions in the current request.\n9. If you must ask a blocking question, use this compact format: `AskUserQuestion: \u003Cone question> Why it matters: \u003Cdecision it changes>`.\n10. Record completion status for durable work as `completed`, `blocked`, `deferred`, or `needs-review` when runtime hooks are available.\n\nArtifact format policy:\n\n- Default to Markdown for short notes, repo-native documentation, changelog fragments, or artifacts where clean source diffs matter.\n- Use a self-contained HTML file when the user asks for HTML, the artifact is likely to exceed about 100 lines, the reader needs diagrams\u002Ftables\u002Fcomparisons\u002Fscreenshots, the artifact is meant to be shared, or interaction\u002Fexport controls would help the user stay in the loop.\n- Route by product job first, then choose the format. Do not create a generic HTML workflow when a Productize playbook, gate, or routed skill owns the work.\n- HTML artifacts must be local-first and portable: one file, embedded CSS\u002FJS, no remote dependencies unless explicitly requested, readable without a dev server, responsive, accessible, and easy to skim.\n- Prefer semantic sections, tables, SVG diagrams, annotated code blocks, status chips, collapsible detail, and copy\u002Fexport buttons when they improve review speed. Avoid decorative complexity that hides the decision.\n- For implementation work with ambiguities, use `$implementation-notes` when the user asks for a running notes file, especially `implementation-notes.html` or `implementation-notes.md`.\n\nRuntime hooks, if available:\n\n- Use `productize-workflow start \"\u003Cuser request>\"` at the beginning of durable product work; it restores context, routes the request, records the session, and returns the required artifact contract.\n- Use `productize-workflow complete --id \u003Cid> --status completed|blocked|deferred|needs-review --artifact-type \u003Ctype> --summary \u003Csummary>` before ending durable product work; it records the artifact, saves context, and logs completion status.\n- Use `productize-update-check --strict` at the start of maintenance, setup, release, or generated-output work.\n- Use `productize-config` to read or write user\u002Fteam preferences such as persona, artifact mode, evidence threshold, or update-check policy.\n- Use `productize-session-log` to record important workflow decisions.\n- Use `productize-artifact-log` when a durable artifact is produced.\n- Use `productize-context-restore` before restarting long-running product work from scratch.\n- Use `productize-context-save` after producing a durable strategy, research, spec, or stakeholder artifact.\n- Use `productize-registry-search` or `productize-skill-router` when routing is ambiguous.\n- Use `productize-completion-status` to log whether the workflow completed, blocked, deferred, or needs review.\n\nTelemetry standard:\n\n- Keep telemetry local by default in `.productize\u002F` or `PRODUCTIZE_STATE_DIR`.\n- Log artifact type, routing decision, evidence gaps, and completion status; do not log secrets or private customer data unless the user explicitly asks for it.\n\nCurrent skill metadata:\n\n- **Skill**: `wwas`\n- **Lifecycle**: Plan\n- **Category**: Delivery\n- **Primary artifact**: Why-What-Acceptance backlog items with strategic context and acceptance criteria\n\nUse when writing backlog items in Why-What-Acceptance format, breaking features into independent valuable work, or adding strategic context to delivery items.\n\n## Productize Contract\n\n- **Primary lifecycle**: Plan\n- **Supporting lifecycle**: Build With AI\n- **Primary artifact**: Why-What-Acceptance backlog items with strategic context and acceptance criteria\n- **Source method**: pm-skills-main\u002Fpm-execution\u002Fskills\u002Fwwas\u002FSKILL.md\n\n## Method\n\nCreate product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.\n\n**Use when:** Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.\n\n**Arguments:**\n- `$PRODUCT`: The product or system name\n- `$FEATURE`: The new feature or capability\n- `$DESIGN`: Link to design files (Figma, Miro, etc.)\n- `$ASSUMPTIONS`: Key assumptions and strategic context\n\n## Step-by-Step Process\n\n1. **Define the strategic Why** - Connect work to business and team objectives\n2. **Describe the What** - Keep descriptions concise, reference designs\n3. **Write Acceptance Criteria** - High-level, not detailed specifications\n4. **Ensure independence** - Items can be developed in any order\n5. **Keep items negotiable** - Invite team conversation, not constraints\n6. **Make items valuable** - Each delivers measurable user or business value\n7. **Ensure testability** - Outcomes are observable and verifiable\n8. **Size appropriately** - Small enough for one sprint estimate\n\n## Item Template\n\n**Title:** [What will be delivered]\n\n**Why:** [1-2 sentences connecting to strategic context and team objectives]\n\n**What:** [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]\n\n**Acceptance Criteria:**\n- [Observable outcome 1]\n- [Observable outcome 2]\n- [Observable outcome 3]\n- [Observable outcome 4]\n\n## Example WWA Item\n\n**Title:** Implement Real-Time Spending Tracker\n\n**Why:** Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.\n\n**What:** Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.\n\n**Acceptance Criteria:**\n- Spending totals update within 2 seconds of logging an expense\n- Budget progress is visually indicated with a progress bar\n- Users can see remaining budget amount at a glance\n- System handles multiple expense categories correctly\n\n## Output Deliverables\n\n- Complete set of backlog items for the feature\n- Each item includes Why, What, and Acceptance Criteria sections\n- Items are independent and deliverable in any order\n- Items are sized for estimation and completion in one sprint\n- Strategic context is clear for team decision-making\n- Design references are included for implementation guidance\n\n---\n\n### Further Reading\n\n- [How to Write User Stories: The Ultimate Guide](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fhow-to-write-user-stories)\n\n## Productize Output Rules\n\n- Produce the artifact named in the Productize contract, not a generic framework summary.\n- Separate known facts, assumptions, missing evidence, and risky leaps before recommending.\n- Convert uncertain claims into validation steps, metrics, owner decisions, or launch\u002Freadout checks.\n- If this reference method conflicts with Productize evidence standards, keep the Productize standard.\n",{"name":5,"description":7},"main","f177680a573a242a81bd0a776f9681f620e6d74c","skills\u002Fproductize-wwas",0,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize","https:\u002F\u002Fgithub.com\u002Fitseffi","2026-08-07 20:07:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add itseffi\u002Fproductize --skill productize-wwas",{"tool":37,"command":38},"bunx","bunx skills add itseffi\u002Fproductize --skill productize-wwas",{"tool":40,"command":41},"pnpm","pnpm dlx skills add itseffi\u002Fproductize --skill productize-wwas","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-wwas\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",315,"https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-wwas\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7357QB5M87V95F82E73V2TF","workflow-memory","Maintains workflow-scoped task memory for Productize runs using .productize\u002Ftasks\u002F\u003Cname>\u002Fmemory\u002F files. Use when a task prompt provides workflow memory paths and requires the agent to read, update, compact, and promote durable context across PRD task executions. Do not use for PR review remediation, global user preferences, or programmatic event-log summarization.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-memory\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7357K97HSYEHAQTW5ZKM4CE","review-round","Performs a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Freview-round\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7357F2NZE5NSYM2SJXEGBFZ","productize","Productize root skill for building, shipping, operating, and growing AI products inside a coding harness. Routes work across thesis framing, discovery, research, positioning, finance, decision making, requirements, design, metrics, AI-builder execution, code implementation, verification, stakeholder narratives, growth, launch, operation, and learning workflows. Use when the user wants to build a product from zero, improve an existing product, or needs product work that spans multiple lifecycle stages before code, launch, operation, or growth execution.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M735783CDA9MQ0SPR9X6QZSE","productize-writing-plans","Create comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-writing-plans\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M735750V5Q6WRBX1ZFGNRMEB","productize-write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea into a structured document, scoping goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into phases.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-write-spec\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M735723Y1JEQ32YKBNW2WPE8","productize-write-query","Write optimized SQL for a specific dialect with best practices. Use when translating a natural language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a large partitioned-table query, or getting Snowflake, BigQuery, Postgres, or other dialect syntax.","https:\u002F\u002Fgithub.com\u002Fitseffi\u002Fproductize\u002Fblob\u002Fmain\u002Fskills\u002Fproductize-write-query\u002FSKILL.md",[],[]]