create-yss-spec 3.5.2 → 3.5.3

package/template/.agents/skills/setup-matt-pocock-skills/domain.md

@@ -1,37 +0,0 @@
-# Domain Docs
-
-How the engineering skills should consume this repo's domain documentation when exploring the codebase.
-
-## Before exploring, read these
-
-- **`CONTEXT.md`** — the single case-sensitive glossary at the Git repository root. Its `context_schema_version` must be supported. A missing root file, lowercase or nested replacement, duplicate, or map-based layout is `blocked` / `migration-required`, not an optional omission.
-- **`docs/adr/`** — if it exists, read ADRs that touch the area you're about to work in. This directory is created lazily when the first qualifying decision is accepted.
-
-When the repository exposes `scripts/verify-context-contract`, run it before creating or changing stable domain, product, architecture, implementation, review, release, or retrospective assets.
-
-## File structure
-
-Every YSS Git repository:
-
-```
-/
-├── CONTEXT.md
-├── docs/adr/
-│   ├── 0001-event-sourced-orders.md
-│   └── 0002-postgres-for-write-model.md
-└── src/
-```
-
-Multiple business responsibility areas do not create additional glossary files. Each stable business term records its approved PascalCase `适用业务责任区`, and consumers reference it as `<ContextId>/<EnglishIdentifier>`. Use `Global/<EnglishIdentifier>` only for language that is genuinely shared across responsibility areas.
-
-## Use the glossary's vocabulary
-
-When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term and stable reference defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids.
-
-If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `/domain-modeling`).
-
-## Flag ADR conflicts
-
-If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
-
-> _Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…_

package/template/.agents/skills/to-questionnaire/SKILL.md

@@ -1,55 +0,0 @@
----
-name: to-questionnaire
-description: Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
-disable-model-invocation: true
----
-
-Turn something the user can't answer alone into a **questionnaire** — a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.
-
-**Grill the send, not the subject.** Interview the user only about the _send_, which they can always answer: who it goes to, and what they need back. The questions in the document then target the **gap** between what the recipient knows and what the user needs.
-
-Reuse the recipient, purpose and constraints already provided. Ask only for missing information that changes the questionnaire; when both are known, draft directly.
-
-1. **Who is it going to?** If missing, ask for the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.
-
-2. **What do you need back?** If missing, ask for the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.
-
-3. **Write the questionnaire.** Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to `to-questionnaire-<slug>.md` in the current directory (slug from the topic) and report the path. Done when the file exists and every item the user named in step 2 is covered by a question.
-
-## Document structure
-
-Frame the document as a **discovery questionnaire**: the user lacks context, the recipient holds it. Order questions most-important-first — async means you may only get one pass — and group them under `##` headings by theme once there are more than a handful. Write it using the template below.
-
-<questionnaire-template>
-
-# <Questionnaire title>
-
-**Purpose:** why this questionnaire exists and the decision riding on it.
-
-**From:** <the user> — **To:** <the recipient> — **How your answers will be used:** <where they go>
-
-## Context
-
-One paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.
-
-## How to answer
-
-Deadline and rough effort. Partial answers and "I don't know" are useful — flag anything you're unsure of rather than skipping it.
-
-## <Theme heading>
-
-One `##` section per theme. Under each, its questions, most-important-first. Every question is one idea — never compound — with an answer stub directly beneath, and a one-line _why this matters_ only where the question could be misread or invite a throwaway answer.
-
-<question-example>
-### What load is the system expected to handle at launch?
-
-_Why this matters: it decides whether we provision for burst traffic now or defer it._
-
->
-</question-example>
-
-## Anything else?
-
-A closing catch-all: anything we didn't ask that we should know?
-
-</questionnaire-template>

package/template/.agents/skills/to-questionnaire/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "To Questionnaire"
-  short_description: "Front-load questions into a doc for someone to answer"
-policy:
-  allow_implicit_invocation: false

package/template/.agents/skills/wait-what/SKILL.md

@@ -1,7 +0,0 @@
----
-name: wait-what
-description: "Stop. That last message did not land: re-pitch it."
-disable-model-invocation: true
----
-
-用用户当前使用的语言，补足刚才说明所缺的背景并重新解释。保持简明、具体，复用仓库根目录唯一 `CONTEXT.md` 的词汇；跨业务责任区按 `<ContextId>/<EnglishIdentifier>` 定位。只改表达，不启动完整生命周期或重建上下文。

package/template/.agents/skills/wait-what/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Wait What"
-  short_description: "Re-pitch that — simpler, with the context I'm missing"
-policy:
-  allow_implicit_invocation: false

package/template/.codex/skills/data-analytics/.app.json

@@ -1,84 +0,0 @@
-{
-  "apps": {
-    "slack": {
-      "id": "REPLACE_WITH_SLACK_APP_OR_CONNECTOR_ID"
-    },
-    "teams": {
-      "id": "connector_246af0940da3457da0e751171dc1ce60",
-      "optional": true
-    },
-    "notion": {
-      "id": "REPLACE_WITH_NOTION_APP_OR_CONNECTOR_ID"
-    },
-    "gmail": {
-      "id": "connector_2128aebfecb84f64a069897515042a44",
-      "optional": true
-    },
-    "outlook_email": {
-      "id": "connector_4aaab2856305417b993eca9a216aaf6e",
-      "optional": true
-    },
-    "outlook_calendar": {
-      "id": "connector_e6a7394682e24467ac68c60696f275a4",
-      "optional": true
-    },
-    "google_calendar": {
-      "id": "connector_947e0d954944416db111db556030eea6",
-      "optional": true
-    },
-    "google_drive": {
-      "id": "connector_5f3c8c41a1e54ad7a76272c89e2554fa"
-    },
-    "databricks": {
-      "id": "templated_apps_Databricks",
-      "optional": true
-    },
-    "bigquery": {
-      "id": "connector_7c3f2c8cdbf64bb0b183ff52f527a06e",
-      "optional": true
-    },
-    "snowflake": {
-      "id": "templated_apps_Snowflake",
-      "optional": true
-    },
-    "sharepoint": {
-      "id": "connector_1e4f6a44acf14e3ca1d96672f8c945bc",
-      "optional": true
-    },
-    "github": {
-      "id": "connector_76869538009648d5b282a4bb21c3d157"
-    },
-    "statsig": {
-      "id": "REPLACE_WITH_STATSIG_APP_OR_CONNECTOR_ID",
-      "optional": true
-    },
-    "hex": {
-      "id": "REPLACE_WITH_HEX_APP_OR_CONNECTOR_ID",
-      "optional": true
-    },
-    "deepnote": {
-      "id": "REPLACE_WITH_DEEPNOTE_APP_OR_CONNECTOR_ID",
-      "optional": true
-    },
-    "amplitude": {
-      "id": "REPLACE_WITH_AMPLITUDE_APP_OR_CONNECTOR_ID",
-      "optional": true
-    },
-    "mixpanel": {
-      "id": "REPLACE_WITH_MIXPANEL_APP_OR_CONNECTOR_ID",
-      "optional": true
-    },
-    "omni-analytics": {
-      "id": "REPLACE_WITH_OMNI_ANALYTICS_APP_OR_CONNECTOR_ID",
-      "optional": true
-    },
-    "metabase": {
-      "id": "templated_apps_Metabase",
-      "optional": true
-    },
-    "thoughtspot": {
-      "id": "REPLACE_WITH_THOUGHTSPOT_APP_OR_CONNECTOR_ID",
-      "optional": true
-    }
-  }
-}

package/template/.codex/skills/data-analytics/.codex-plugin/plugin.json

@@ -1,66 +0,0 @@
-{
-  "name": "data-analytics",
-  "version": "0.1.34",
-  "description": "Analyze product usage, investigate metric movements, prepare KPI reports, build high-quality dashboards and notebooks, create source-backed semantic layers, guide first-run analytics setup, and generate analytics-grade report apps.",
-  "author": {
-    "name": "Data Analytics Maintainers"
-  },
-  "homepage": "https://github.com/openai/role-specific-plugins",
-  "repository": "https://github.com/openai/role-specific-plugins/tree/main/plugins/data-analytics",
-  "license": "MIT",
-  "keywords": [
-    "data-analytics",
-    "analytics",
-    "business-context",
-    "dashboards",
-    "funnel-analysis",
-    "kpi-reporting",
-    "market-sizing",
-    "metric-diagnostics",
-    "post-launch-updates",
-    "product-analysis",
-    "retention",
-    "root-cause-analysis",
-    "scorecards",
-    "validation",
-    "visualization",
-    "jupyter-notebooks",
-    "databricks",
-    "bigquery",
-    "snowflake",
-    "deepnote",
-    "mixpanel",
-    "mixpanel-headless",
-    "metabase",
-    "thoughtspot",
-    "onboarding",
-    "semantic-layer"
-  ],
-  "skills": "./skills/",
-  "apps": "./.app.json",
-  "mcpServers": "./.mcp.json",
-  "interface": {
-    "displayName": "Data Analytics",
-    "shortDescription": "Turn data into clear decisions",
-    "longDescription": "Turn analytical questions into validated answers, dashboards, reports, notebooks, and clear recommendations. Explore product and business data, explain why key metrics changed, design KPIs, size opportunities, check data quality, and save reusable metric and source context for future work.\n\nStart with connected warehouses, BI tools, product analytics, docs, chat, spreadsheets, or uploaded files. Guided onboarding helps you connect core tools and set up reusable data context, while interactive charts, tables, dashboards, and report apps keep the evidence reviewable and ready to share.",
-    "developerName": "OpenAI",
-    "category": "Analytics",
-    "capabilities": [
-      "Interactive",
-      "Read",
-      "Write"
-    ],
-    "websiteURL": "https://openai.com/",
-    "privacyPolicyURL": "https://openai.com/policies/privacy-policy/",
-    "termsOfServiceURL": "https://openai.com/policies/terms-of-use/",
-    "defaultPrompt": [
-      "Help me get started and set up reusable data context for future data work",
-      "Analyze product usage and recommend where the team should focus next",
-      "Diagnose why a key metric changed and identify the biggest drivers"
-    ],
-    "brandColor": "#0285FF",
-    "composerIcon": "./assets/datascience-small.svg",
-    "logo": "./assets/datascience.png",
-    "screenshots": []
-  }
-}

package/template/.codex/skills/data-analytics/.mcp.json

@@ -1,30 +0,0 @@
-{
-  "mcpServers": {
-    "datascienceWidgets": {
-      "title": "Data Analytics Widgets",
-      "description": "Render Data Analytics charts, tables, dashboards, and report artifacts.",
-      "icons": [
-        {
-          "src": "./assets/datascience-small.svg",
-          "mimeType": "image/svg+xml",
-          "sizes": [
-            "24x24"
-          ]
-        },
-        {
-          "src": "./assets/datascience.png",
-          "mimeType": "image/png",
-          "sizes": [
-            "360x360"
-          ]
-        }
-      ],
-      "cwd": ".",
-      "command": "node",
-      "args": [
-        "./mcp/server.cjs",
-        "--stdio"
-      ]
-    }
-  }
-}

package/template/.codex/skills/data-analytics/AGENTS.md

@@ -1,20 +0,0 @@
-# Data Analytics MCP Apps
-
-## Purpose
-
-This plugin contains a complex fullscreen analytics artifact workspace plus compact inline chart and table widgets. Preserve that architecture when iterating: artifacts are snapshot-first workspaces, while chart and table widgets are focused views of reviewed query results.
-
-## Visual Style
-
-Follow the local Codex style contract in `src/codex-style-contract.md`.
-`src/styles/codex-theme.css` is the copied Codex fallback baseline and must load before `src/analytics-app/tokens.css`. Shared surfaces, controls, typography, spacing, borders, radii, shadows, focus, and motion should resolve through the Codex tokens. Analytics CSS may extend the baseline for charts, KPI states, tables, report widths, and dashboard layouts.
-
-## Fullscreen Behavior
-
-Inline surfaces that support fullscreen expose a compact top-right fullscreen control and hide it after fullscreen is active.
-
-## Workflow
-
-Before future changes, start with the installed `codex-mcp-app-devkit` skill so it can route to the app-development workflow and the Codex visual references. Use `npm run preview:widgets` for local previews, `npm run build` for all widget bundles, `npm run typecheck` for TypeScript, and `npm test` for MCP server and widget contract coverage.
-
-The plugin package is materialized directly from this directory. After changing widget source, run `npm run build` so `assets/` and normalized bundle parts stay aligned, then reinstall the updated development plugin from the Plugin Development marketplace when testing inside Codex.

package/template/.codex/skills/data-analytics/DEPENDENCIES.MD

@@ -1,27 +0,0 @@
-# Dependencies
-
-## How tool references work
-
-Data Analytics plugin files use lane placeholders such as `~~structured_data` for whatever source the user connects or provides in that category. For example, `~~structured_data` might mean a warehouse connector, SQL runner, API/CLI result, pasted query output, uploaded file, or schema description.
-
-The plugin is tool-agnostic. It describes workflows in terms of analysis lanes rather than one required stack. Direct connectors give the best experience, but the workflows should still be useful with pasted results, SQL snippets, screenshots, exports, or uploaded files.
-
-## Dependencies for this plugin
-
-| Category | Placeholder | Providers | Purpose |
-| --- | --- | --- | --- |
-| Data warehouse | `~~structured_data` | Databricks, BigQuery, Snowflake, Redshift, PostgreSQL, MySQL | Query tables, explore schemas, and produce result sets. Databricks, BigQuery, and Snowflake are declared in `.app.json` as app-backed connector choices. |
-| Notebook lab | `~~notebook_lab` | Hex, Deepnote, Jupyter | Iterate, preserve reusable code, and support richer exploratory work. Hex and Deepnote are declared in `.app.json` as app-backed connector choices. |
-| Behavior signals | `~~behavior_signals` | Amplitude, Mixpanel, Mixpanel Headless | Analyze product event trends and funnels. Amplitude and Mixpanel are declared in `.app.json`; Mixpanel Headless is a companion plugin/skill path when installed. |
-| Dashboards and BI | `~~dashboards_or_bi` | ThoughtSpot, Omni Analytics, Metabase, dashboard/BI app | Inspect dashboard metadata, metric definitions, widget SQL, and BI answers. ThoughtSpot, Omni Analytics, and Metabase are declared in `.app.json` as app-backed connector choices. |
-| Team communication | `~~team_communication` | Slack, Microsoft Teams | Search recent decisions, blockers, owner confirmations, and links to durable artifacts |
-| Email context | `~~email_context` | Gmail, Outlook Email | Inspect relevant message threads, stakeholder context, and follow-up history |
-| Calendar context | `~~calendar_context` | Outlook Calendar | Check meeting timing, attendees, and operating cadence context |
-| Company docs | `~~company_docs` | Google Drive, SharePoint, Google Docs, Google Slides, Notion | Read workspace knowledge, PRDs, metric docs, strategy docs, and source caveats |
-| Sheet workspace | `~~spreadsheet_workspace` | Google Drive, SharePoint, Google Sheets | Review small exports, manual QA, and stakeholder-friendly tables |
-| Presentation surface | `~~presentation_surface` | Google Drive, SharePoint, Google Docs, Google Slides | Create final charts, dashboards, and share-ready narratives |
-| Code repository | `~~code_repository` | GitHub, local checkout | Inspect source logic, model SQL, lineage, tests, and repo context |
-| Files, notebooks, or spreadsheets | `~~files_and_notebooks` | Google Drive, SharePoint, local files, uploaded files, notebooks, spreadsheets | Use local or uploaded analysis inputs, notebooks, CSVs, and spreadsheets |
-| Application hosting | `~~application_hosting` | Site Creator | Host reports, deployed app links, and previewable interactive artifacts |
-| Planning tracker | `~~planning_tracker` | Atlassian, Linear, Asana, Jira | Track analysis requests, owners, deadlines, and dependencies |
-| Data operations | `~~operations_logs` | Airflow | Check pipeline freshness, model ownership, lineage, and outage context |

package/template/.codex/skills/data-analytics/README.md

@@ -1,60 +0,0 @@
-# Data Analytics
-
-Answer product and business questions with data, explain why metrics changed, and turn analysis into reports, dashboards, and clear decisions.
-
-## When to use this plugin
-
-Use Data Analytics when you need to understand product or business performance, explain why a metric changed, define a success measurement plan, assess whether data is trustworthy, or package analysis for stakeholders. You can start from connected data in a data warehouse, dashboards, notebooks, spreadsheets, uploaded files, or pasted context.
-
-## Onboarding
-
-Ask Codex:
-
-`@Data Analytics Help me get started and set up reusable data context for future data work`
-
-Data Analytics has a guided onboarding flow that helps confirm the right data sources, save reusable metric and source-of-truth context you provide, and build a context-specific first analysis prompt.
-
-Onboarding is an interactive, step-by-step conversation. Codex will guide you through setup, ask for approval before making changes, and help you try a first workflow.
-
-Already have a focused task? Start directly with one of the workflows below.
-
-## Example workflows
-
-The primary hero workflow is bolded.
-
-| Workflow | Try this | Skill | Result |
-| --- | --- | --- | --- |
-| **Analyze a product or business question** | `Analyze activation and recommend where the team should focus next` | `product-business-analysis` | A decision-ready analysis with evidence, measurable opportunities, and a clear recommendation |
-| Diagnose a metric movement | `Diagnose why weekly active users dropped last week` | `metric-diagnostics` | A calibrated explanation of verified drivers, likely contributors, unresolved questions, and next actions |
-| Design KPIs | `Design a KPI framework for this new product area` | `design-kpis` | A measurement plan with outcome metrics, drivers, guardrails, targets, and validation priorities |
-| Prepare a KPI readout | `Turn this month's metrics into a leadership-ready operating update` | `kpi-reporting` | A concise KPI update with actuals, comparisons, validated drivers, and operating implications |
-| Build a dashboard | `Build a dashboard for monitoring activation, retention, and conversion` | `build-dashboard` | A source-backed dashboard with metrics, filters, visual hierarchy, QA, and handoff |
-| Size a market | `Estimate the market opportunity for this product and show the assumptions` | `market-sizing` | A transparent market or opportunity sizing estimate with sensitivity, uncertainty, and validation priorities |
-| Build an analytical report | `Create an executive report explaining the biggest growth drivers this quarter` | `build-report` | A polished report with answer-first narrative, charts, tables, caveats, and source metadata |
-| Improve or render a chart | `Turn this analysis into a clear chart for the product review` | `visualize-data` | A production-ready visual with the right chart type, labels, hierarchy, and accessibility checks |
-| Create a notebook | `Build a reproducible notebook for this experiment readout` | `jupyter-notebooks` | A clean SQL or Python notebook that can be skimmed, rerun, and extended |
-| Work with spreadsheets | `Analyze this workbook and add a polished summary tab` | `spreadsheets` | A verified spreadsheet artifact with formulas, formatting, charts, tables, and a clear readout |
-| Validate an analysis | `Review this analysis before I share it with leadership` | `validate-data` | A QA pass covering methodology, sources, calculations, analytical pitfalls, caveats, and conclusion strength |
-| Assess data quality | `Check whether this table is reliable enough for our retention analysis` | `analyze-data-quality` | A source-backed quality assessment covering grain, freshness, missingness, duplicates, joins, and material risks |
-
-## Integrations
-
-Data Analytics can use available tools when they are connected:
-
-| Source | Supported integrations | What they unlock |
-| --- | --- | --- |
-| Warehouses and query tools | Databricks, Databricks Genie, BigQuery, Snowflake | Schema inspection, query-backed analysis, and source-grounded metric investigation |
-| Product analytics and BI | Amplitude, Mixpanel, Omni Analytics, Metabase, ThoughtSpot, Statsig | Behavior analysis, dashboard context, experiment evidence, and reusable reporting inputs |
-| Notebooks and analytical workspaces | Hex, Deepnote | Reproducible analysis, notebook handoff, and shared analytical context |
-| Docs and collaboration | Google Drive, SharePoint, Notion, GitHub, Slack, Microsoft Teams | Business definitions, source-of-truth documents, implementation context, and stakeholder evidence |
-| Email and calendar | Gmail, Outlook Email, Outlook Calendar | Supporting context for stakeholder questions, operating cadence, and analytical handoff |
-
-You can also start with spreadsheets, uploaded files, pasted query results, schema descriptions, or manually provided business context.
-
-## Local development
-
-The published plugin does not require users to install Node.js dependencies. For local development of the Data Analytics MCP server and widgets, install dependencies from the plugin directory:
-
-```sh
-npm ci
-```

package/template/.codex/skills/data-analytics/__yss_dotfile__.gitignore

@@ -1,2 +0,0 @@
-node_modules/
-dist/

package/template/.codex/skills/data-analytics/assets/datascience-artifact-widget.html

@@ -1,16 +0,0 @@
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="utf-8" />
-    <title>Data Analytics artifact app</title>
-    <script type="module">
-      const target = new URL("../src/datascience-artifact-widget.html", import.meta.url);
-      target.search = window.location.search;
-      window.location.replace(target);
-    </script>
-  </head>
-  <body>
-    <p>Redirecting to the local widget source for development.</p>
-    <p><a href="../src/datascience-artifact-widget.html">Open Data Analytics artifact app</a></p>
-  </body>
-</html>