「plan」の検索結果

Sequenced launcher that bootstraps QA on a project with no QA in place. Chains qa-project-context → test-strategy → test-planning in one guided run, then points you at automation. Use when: "set up QA on a new project," "QA from scratch," "no QA exists yet," "/qa-start." Not for: onboarding a QA engineer to an existing team with existing tests — use qa-project-bootstrap. Not for: "which skill do I use" with no clear match — use qa-do. Related: qa-project-context, test-strategy, test-planning, qa-project-bootstrap, qa-do.

日本語の概要は準備中です。原文の説明を表示しています。

Validate that analytics and marketing tracking fire CORRECTLY: GA4/GTM dataLayer events, Meta/TikTok/LinkedIn pixels, and ad-tech tags. Covers building a tracking plan as the contract, intercepting collect-endpoint beacons and dataLayer.push in Playwright, asserting event name + params + values + timing + de-duplication, Consent Mode v2 gating, CI regression gating, and news-media events (article-view, scroll-depth, paywall). Use when: "test analytics tracking," "GA4 event test," "verify the pixel fires," "dataLayer test," "tracking plan," "Meta Pixel dedup," "scroll-depth tracking test," "gate tracking in CI." Not for: whether tracking is ALLOWED to fire under consent law (GDPR/CMP) — that is compliance-testing; this skill checks the data is CORRECT. SEO meta tags / structured data — out of scope. Related: compliance-testing, playwright-automation, api-testing, qa-project-context.

日本語の概要は準備中です。原文の説明を表示しています。

Author and maintain MANUAL and hybrid test cases and suites in TestRail, Xray (Jira), Zephyr Scale, and Qase. Covers test-case anatomy (title, preconditions, steps, expected results, test data), suite/section organization, bulk authoring from user stories and acceptance criteria, ambiguous-step linting, CSV/API import-export payloads per tool, requirement traceability and coverage gaps, review hygiene, and when a manual case should graduate to automation. Use when: "write a test case," "manual test case," "TestRail case," "Xray test," "Zephyr Scale case," "Qase case," "import CSV into TestRail," "lint these steps," "traceability report," "should this be automated." Not for: Generating automated TEST CODE — that is ai-test-generation. Sprint-level WHAT-to-test selection — that is test-planning. Related: ai-test-generation, test-planning, exploratory-testing, qa-project-context.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an instructor asks for a MATLAB Grader assessment setup guide, adoption guide, pilot plan, course-specific rollout, QTI 3 sharing workflow, or recommended MATLAB Grader assessment-item-generation configuration based on a learning objective, course title, course description, module description, lab description, or assessment goal.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an instructor asks for a MATLAB AI tutor setup guide, adoption guide, pilot plan, course-specific rollout, or recommended tutor configuration based on a learning objective, course title, course description, module description, or lab description.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a structured implementation plan from an evidence draft. Validate paths, obtain configured independent Codex and Qoder reviews, synthesize available advice against repository evidence, preserve the draft, and produce testable acceptance criteria and validation steps.

日本語の概要は準備中です。原文の説明を表示しています。

Creates and manages project roadmaps with milestones and PRD queues. Use after architecture is defined for project planning. Triggers on: create roadmap, plan milestones, organize prds.

日本語の概要は準備中です。原文の説明を表示しています。

Generates Product Requirements Documents (PRD) for new features. Use when planning features or starting projects. Triggers on: create prd, write prd, plan feature, requirements, spec out.

日本語の概要は準備中です。原文の説明を表示しています。

Build a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market. Triggers on requests to plan HN/Reddit launch, "Show HN" post, community launch, or when user asks "HN launch", "Show HN", "Reddit launch", "launch on /r/SaaS", "Product Hunt vs HN", "community launch", "developer launch". Outputs GTM-* with Type=Channel-HN / Type=Channel-Reddit entries with timing, title, story angle, and engagement plan.

日本語の概要は準備中です。原文の説明を表示しています。

Transform v0.6 specifications into context-window-sized work packages (EPICs) during PRD v0.7 Build Execution. Triggers on requests to create epics, scope work, break down implementation, or when user asks "create epics", "scope work", "break down work", "context window sizing", "what to build first?", "implementation planning", "epic breakdown". Consumes API-, DBT-, FEA-, ARC-. Outputs EPIC- entries with objectives, ID references, dependencies, and context windows. Feeds v0.7 Test Planning.

日本語の概要は準備中です。原文の説明を表示しています。

Assess adoption-lifecycle stage, plan the chasm crossing, and build a beachhead strategy using Geoffrey Moore's Crossing the Chasm framework during PRD v1.0 Market Adoption. Triggers on requests to assess adoption stage, plan beachhead, cross the chasm, scale from early adopters, or when user asks "are we in the chasm?", "crossing the chasm", "beachhead strategy", "Moore", "whole product", "pragmatist buyers", "from early adopters to early majority". Outputs ADO-STAGE-*, ADO-BEACHHEAD-*, ADO-WHOLE-*, ADO-REF-* entries.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate go-to-market strategy by running positioning, offer construction, and channel allocation as a sequenced workflow during PRD v0.9 Go-to-Market. Triggers on requests to plan launch, define GTM strategy, or when user asks "how do we launch?", "go-to-market", "launch plan", "marketing strategy", "GTM", "launch this product". Chains three framework-grounded sub-skills (Dunford → Hormozi → ORB) and reconciles their outputs.

日本語の概要は準備中です。原文の説明を表示しています。

Survey a whole React codebase as a senior React engineer, using React Doctor's scan as evidence, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the React code", "audit this codebase", "make this app faster / more robust", or wants a roadmap of fixes rather than a review of a single diff. For a regression check or a fix-it-now pass, use the `react-doctor` skill instead.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants a Xiaohongshu posting calendar, weekly review board, first-10-post launch plan, 10-20-post positioning test, or data-based next-step plan. Trigger phrases: "排期", "复盘", "30 天计划", "前10条", "10-20条测试", "发了没数据", "weekly review", "content calendar", "XHS schedule". Do not use for first-draft editing or initial account positioning.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or developing content strategy. For deep SEO writing optimization, see the seo-content-writer skill.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants a Xiaohongshu posting calendar, weekly review board, first-10-post launch plan, 10-20-post positioning test, or data-based next-step plan. Trigger phrases: "排期", "复盘", "30 天计划", "前10条", "10-20条测试", "发了没数据", "weekly review", "content calendar", "XHS schedule". Do not use for first-draft editing or initial account positioning.

日本語の概要は準備中です。原文の説明を表示しています。

Audit project dependencies for outdated packages, security vulnerabilities, and breaking changes. Use when someone asks to "check for outdated packages", "audit dependencies", "find vulnerable dependencies", "plan dependency upgrades", "detect breaking changes", or "update npm packages safely". Analyzes package.json/lock files, cross-references changelogs, and produces ordered upgrade plans.

日本語の概要は準備中です。原文の説明を表示しています。

Plans and scripts data migrations between SQL databases: schema mapping, type conversion, batched and resumable loading, validation and cutover. Use when the user mentions "data migration," "database migration," "migrate from MySQL to PostgreSQL," "schema migration," "ETL pipeline," "data transfer," "database consolidation," "legacy migration," or "move data between databases." Covers schema analysis, mapping, transformation, batch processing, validation, and cutover planning. For query optimization during migration, see sql-optimizer.

日本語の概要は準備中です。原文の説明を表示しています。

Read and apply a project-specific BUILDING_SPEC.md or DIMENSIONS.md file before generating any architectural elements. Use when: generating floor plans, 3D buildings, or any spatial design where the project has defined custom dimensions, room requirements, or design standards.

日本語の概要は準備中です。原文の説明を表示しています。

Reference for architectural dimensions, proportions, and building codes for AI-generated 3D/2D models. Use when: generating floor plans, creating 3D buildings, validating architectural designs, ensuring correct human-scale proportions in models.

日本語の概要は準備中です。原文の説明を表示しています。

Designs and implements website analytics tracking with Google Analytics 4 and Google Tag Manager: a written tracking plan, event and parameter names that pass GA4's rules, gtag.js or data-layer code, key events, consent mode, UTM conventions, and a verification pass. Use when someone says "set up GA4", "add conversion tracking", "track this form or button", "write a tracking plan", "GTM data layer", "UTM parameters", "why are my events missing or counted twice", or "audit our analytics setup".

日本語の概要は準備中です。原文の説明を表示しています。

Use when computing orbits, planning maneuvers, propagating trajectories, or analyzing orbital perturbations for spacecraft or celestial bodies. Use when "orbit, trajectory, maneuver, delta-v, Hohmann, Keplerian, perturbation, J2, TLE, orbital elements, semi-major axis, eccentricity, inclination, RAAN, spacecraft propagation, Lambert solver, interplanetary, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Power systems engineering covering grid modeling, power flow analysis, energy storage dispatch, demand response, and electricity market economics. Spans transmission/distribution planning to real-time operations. Use when "power flow|load flow|grid model, energy storage|battery dispatch|ESS, demand response|load management|peak shaving, electricity market|LMP|locational marginal price, grid stability|frequency|voltage, capacity planning|resource adequacy, unit commitment|economic dispatch, transmission|distribution|power system, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

World-class content strategy expertise combining the frameworks of Andy Crestodina's data-driven approach, Ann Handley's "everybody writes" philosophy, and the content engines that power companies like HubSpot, Ahrefs, and Intercom. Content strategy isn't about creating content - it's about creating the right content for the right audience at the right time in the right format. The best content strategists think in systems, not pieces. They build content engines that compound over time and turn strangers into customers and customers into advocates. Use when "content strategy, content plan, editorial calendar, blog strategy, content marketing, topic clusters, pillar content, content audit, content calendar, SEO content, content distribution, content funnel, thought leadership, content engine, content topics, what to write, content, strategy, editorial, SEO, blog, planning, distribution, measurement" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。